01
Software Architecture
Shaping systems so that domain boundaries, data ownership, and change remain explicit. Architecture as a set of decisions with consequences — not a diagram produced after the code exists.
$Medellín, Colombia
David Ricardo González Zapata
Senior Software Engineer / Software Architect
Designing scalable systems, distributed architectures and high-performance platforms.
$stack
full inventory →- PHP
- Laravel
- Symfony
- Python
- Node.js
- TypeScript
- React
- Next.js
- PostgreSQL
- Redis
- Docker
- Kubernetes
$Stack
Technical stack
Backend, workers, data and delivery used in production work — PHP, Laravel, Symfony, Python, Node.js, TypeScript, React, Next.js, PostgreSQL, Redis, Docker, Kubernetes, and the rest of the working set.
Backend
- PHP
- Laravel
- Symfony
- Python
- Node.js
- TypeScript
- Express
- JSON:API
- GraphQL
- CakePHP
- Yii
Frontend
- React
- Next.js
- Vue.js
- TypeScript
- JavaScript
- Tailwind CSS
- Apollo
- HTML
- CSS
- jQuery
Data
- PostgreSQL
- MySQL
- Oracle
- MongoDB
- Redis
Infrastructure
- Docker
- Kubernetes
- Nginx
- Helm
- Google Cloud
- Object storage (S3 / Spaces)
- Memcached
- Supervisor
- Commerce Tools
- Clerk
Messaging
- Redis Streams
- RabbitMQ
- BullMQ
- Socket.IO
Technologies come from the CV, named roles, and later platform work. Proficiency levels are not shown.
$Engineering identity
Engineering focus
The work is systems: how they are shaped, how they fail, and how teams are able to change them.
02
Backend Engineering
APIs, persistence, and the operational path of a request. PHP and Node.js platforms, relational modeling, and the unglamorous work that keeps business operations correct under load.
03
Distributed Systems
Work that does not fit in a single process: queues, caches, background workers, and the failure modes that appear when those pieces drift. Design for partial failure, not for the happy path alone.
04
Microservices
Service boundaries only where they earn their cost. Independent deployability, explicit contracts, and the operational overhead that comes with splitting a system — accepted only when the domain demands it.
05
Domain-Driven Design
Models that follow the business, not the database schema. Bounded contexts, ubiquitous language, and the discipline of keeping infrastructure out of the domain.
06
Cloud Infrastructure
Runtime, not slides: Google Cloud in production backend work, containers with Docker, orchestration with Kubernetes, and the supporting layer of caches and process supervisors.
07
Performance Engineering
Latency and throughput as design constraints. Caching (Redis, Memcached), query shape, worker supervision, and measuring before changing — because intuition about bottlenecks is usually wrong.
08
Technical Leadership
Coordinating delivery, setting technical direction, and making decisions that other engineers can execute. Research into new technology when it is justified; restraint when it is not.
$Architecture notes
How systems are shaped
Notes that separate personal experience from technical perspective. No invented production stories.
Architecture
Edge responsibilities, domain behind
Client
API Gateway
Auth, route, limits
Service A
Service B
Service C
Technical perspective. The gateway routes; services own the rules.
$Selected systems
Featured projects
Case studies from the systems actually built — ProCrédito v2, Armi, and the Soga engineering platform. Unpublished numbers are omitted, not estimated.
$Career
Progression, not a job list
Analyst → Systems Coordinator → Senior Developer → Development Coordinator → Senior Backend Developer → Technical Lead → Head of R&D.
Analyst →Systems Coordinator →Senior Developer →Development Coordinator →Senior Backend Developer →Technical Lead →Head of R&D
June 2019
— Present
Head of R&D
Head of Software Research and Development
Soga SAS
Lead research and development for the internal engineering platform: hexagonal Laravel services, Python stream workers, and architectural direction for products such as ProCrédito v2.
LaravelPHPPythonRedis StreamsMySQLDockerKubernetesNginxJanuary 2024
— March 2026
Technical Lead
Fullstack Technical Lead
Armirene
Technical lead on Armi, a multi-commerce platform: Commerce Tools as the engine, Checkout and Merchant Center as Next.js products, delivery with Docker and Kubernetes.
Next.jsReactTypeScriptGraphQLCommerce ToolsClerkRabbitMQDockerKubernetesNovember 2019
— August 2023
Senior Backend Developer
Senior Backend Developer
TRIKO SAS
Senior backend engineering with architecture, development practices, and infrastructure on Google Cloud — including Redis, Memcached, and process supervision.
Google CloudRedisMemcachedSupervisorJanuary 2018
— June 2019
Development Coordinator
Development Coordinator
FENALCO Atlántico
Coordinate, design, and implement custom software for organizational needs — including ProCrédito 2.0 and FACTIBLE electronic invoicing.
TODO_TECH_STACK
Concurrent roles are listed separately, with dates as recorded. See the complete history.
$Contact
Start a technical conversation
For senior engineering, technical lead, and software architecture roles. Phone is not published here. No social networks besides GitHub and LinkedIn.
- Location
- Medellín, Colombia
- GitHub
- github.com/ext-rgonzalez