Architecture

Overview of Zoos Global system architecture.

stableArchitecturev2.1intermediatearchitecturesystem-design

1 min readUpdated Jul 24, 2026@platform-teamPlatform Engineering

This document outlines the high-level system architecture of the Zoos Global platforms.

System Topology

Our applications are built on a service-oriented architecture (SOA) leveraging containerized microservices and serverless infrastructure deployed on AWS.

graph TD
  Client[Client Apps / Web] -->|HTTPS| Cloudflare[Cloudflare CDN & WAF]
  Cloudflare -->|Routing| ALB[AWS Application Load Balancer]
  ALB -->|API Gateway| ECS[Amazon ECS Fargate Web Services]
  ECS -->|Queries| Aurora[Amazon Aurora PostgreSQL]
  ECS -->|Events| SQS[Amazon SQS]
  SQS -->|Consume| Workers[Background Workers]
  Workers -->|Cache / Session| ElastiCache[Amazon ElastiCache Redis]

Key Technologies

Frontend: Next.js (React), Astro (for content-rich sites/blogs)
Backend Services: Node.js (NestJS / Fastify), Go (for high-throughput data services)
Databases: PostgreSQL (Aurora Serverless v2), Redis (ElastiCache)
Infrastructure: AWS ECS (Fargate), AWS Lambda, Terraform, Cloudflare

Architectural Patterns

Database-per-Service: Each microservice owns its schema and database instance. Cross-service communication must occur via APIs or event-driven messages, never by direct database connections.
Event-Driven Integration: We use Amazon SQS and SNS for asynchronous event communication between domains to decouple our services.
Twelve-Factor App Methodology: All services must follow Twelve-Factor App principles, notably configuration through environment variables and stateless execution.