infrastructure
High-availability ERP infrastructure
Two application servers, a primary MariaDB with a replica promoted on failure, and Grafana alerting on every environment.
Overview
The hosting layout behind production ERPNext systems. User traffic and API plus cron traffic run on separate application servers so a heavy job never slows the people using the system; both write to one primary MariaDB, and a replica stays in sync and takes over when the primary fails. Deployments go through CI/CD, and Grafana pages on what users would feel.
99%+uptime
2 + 2application and database servers
Features
Topology
- Two application servers: one serves users, one serves API traffic and frequent cron jobs
- One primary MariaDB connected to both application servers
- A replica kept in sync and promoted when the primary fails
- AWS, Azure and GCP: DNS, SSL, backups, scaling
Delivery
- Custom Dockerfiles and Compose environments tuned for build and runtime
- CI/CD pipelines with zero-downtime deployments
- Documented runbooks for every environment
Observability
- Grafana and Prometheus across all managed environments
- Alerts on database health, queue depth, disk, TLS expiry and application errors
- Alerts page on symptoms users would feel, not on every metric
Technical details
- Built with
- MariaDB replication, Docker, CI/CD, Grafana, Prometheus, Ansible, AWS, Azure, GCP
- Type
- infrastructure
- Status
- In production
Private code. Contact me for details.
Have something slow, manual, or fragile in production?
Tell me what it is. I reply within two working days, with questions.
Let's connect