Large-scale applications
Architecture that survives traffic and team growth: clear module boundaries, asynchronous processing, automated deployments and full visibility into production.
Sound familiar?
A monolith where every change breaks something elsewhere.
Microservices introduced too early — complexity without benefit.
Outages detected by customers, not by monitoring.
Manual deployments and fear of Friday deploys.
What it usually looks like inside
- Clientsweb · mobile · API
- Gatewayauth · rate limit
- Domain modulesNestJSQueue / eventsBullMQ · RabbitMQ
- PostgreSQLreplicas · PITRWorkersNode · Python
- ObservabilityGrafana · Loki
The scope you get
Architecture & ADRs
Modular monolith or services — decided by team and domain.
Backend
NestJS / Python / Go, DDD where it pays off, contract tests.
Asynchronous processing
Queues and events for heavy and external operations.
Containers & K8s
Docker, Kubernetes / OpenShift, autoscaling, IaC.
Observability
Logs (Loki), metrics (Prometheus), dashboards and alerts in Grafana.
Code review & mentoring
Standards, reviews and onboarding so the team grows with the system.
Technologies in this area
- Node.js
- NestJS
- Python
- Go
- PostgreSQL
- Docker
- Kubernetes
- OpenShift
- Grafana
- Prometheus
Large-scale applications — FAQ
01Microservices or monolith?
Usually a modular monolith with clear boundaries — faster to build and easy to split later. Microservices when scale or organisation demands it.
02Do you work with an existing team?
Yes — as an architect / tech lead: I design, review, write key modules and mentor.
03Which cloud?
AWS, GCP, Azure, Hetzner or on-premise (OpenShift/OKD). Matched to requirements and budget.
Got a project that has to be fast and work at scale?
Describe it in 2 minutes. I'll reply within 24 hours with first insights and a proposed next step.