Reference architecture
Adjusted per project · not a template
This is what one of our systems looks like inside.
Five layers with separated responsibilities: channels never talk to the database, external integrations never touch the business domain, and every change goes through the same pipeline. It is the starting point of the architecture stage and the document the client's IT team reviews before sign-off.
01
Channels
Channels
Public web
Next.js · TypeScript
Mobile app
React Native
Internal portal
Operations & reporting
02
Edge
Edge
API Gateway
03
Services
Services
Domain
Business rules
Jobs
Queues & retries
Scheduler
Batch processes
Notifications
Outbound events
04
Data
Data
Primary
PostgreSQL
Replica
Read & reporting
Cache
Redis
Backup
Encrypted & verified
05
Third parties
Third parties
Outside the organisation boundary
SUNAT e-invoicing
Payment gateway
ERP / accounting
Messaging & email
Cross-cutting · Observability
Centralised metrics, traces and logs. Alerts land in the channel the client chooses, not in an inbox of ours.
Cross-cutting · Continuity
Recovery objectives agreed in writing, encrypted backups and restores that are tested, not merely scheduled.
Cross-cutting · Delivery
One pipeline for every environment: automated tests, code review and reversible deployment.
Stack by layer
Frontend
React · TypeScript · Next.js · React Native
Backend
Node.js · Python · PHP (Laravel) · REST APIs
Data
PostgreSQL · MySQL · Redis · Analytics dashboards
Infrastructure
AWS · Docker · Linux · CI/CD · 24/7 monitoring
Integrations
Payment gateways · ERP · SUNAT e-invoicing · Messaging
Quality
Automated testing · Backup and recovery · Audit logging
