Web3 Infrastructure Project Overview
This project involved the deployment of a high-availability, multi-stack backend architecture designed for Web3 payment processing.
NOTE
This architecture represents a Development/Staging Environment. It uses a “monolithic-distributed” shared-resource model (sharing a single PostgreSQL and Redis instance across stacks) to maximize resource utilization and minimize infrastructure costs on cloud providers.
It utilizes a “monolithic-distributed” approach where multiple Docker Compose stacks share a single core infrastructure network.
🏗️ Core Architecture
- Network Orchestration: A central infrastructure network allows three distinct stacks to communicate:
- Core Stack: Traefik (Router), PostgreSQL (DB), and Redis (Cache).
- Partner Stack: Auxiliary services for external integrations.
- Listener Stack: Specialized blockchain event listeners (EVM and Solana).
- Reverse Proxy: Traefik acts as the brain of the cluster, handling SSL, routing, and global middleware.
- Backend Framework: NestJS microservices.
🔑 Key Infrastructure Patterns
- Shared Infrastructure: Centralizing DB and Redis prevents resource duplication and simplifies connectivity.
- Service Isolation: Separating “Listeners” and “Partners” into their own Compose files allows for independent scaling and maintenance.
- Secret Management: Uses a
fetch-secrets.shstrategy to pull.envfiles from secure storage (AWS) before startup.
🔗 Deep Dives
- Traefik Routing & Middleware
- Backup & Disaster Recovery
- Prometheus)
- Container Networking & 404 Debugging
Source: Ingested from Internal Infrastructure Manual