How vitabaks/autobase works
Main Components Overview
The system consists of three major parts:
a) Automation Layer (Ansible-based)
b) Console/UI Layer
c) Database Cluster Layer
Key Architectural Components
A. Console Components:
• UI Frontend (React-based)
• Backend Service (Go)
• Console Database (PostgreSQL)
• Docker Integration
B. Database Cluster Components:
• PostgreSQL Instances (Primary/Replicas)
• Patroni (HA Controller)
• DCS (etcd/Consul)
• Load Balancers (HAProxy/Cloud LB)
• Connection Pooler (PgBouncer)
• Monitoring (Netdata)
• Client Layer |
• ↓
• Console Layer |
• UI |→| API Service |←-| Console DB | | Docker Engine | |
• (React) | | (Go) | | (PostgreSQL) | | | |
• ↓
• Automation Layer |
• Ansible Core |→| Playbooks |→| Roles & Tasks | |
• ↓
• Database Cluster Layer |
• PostgreSQL |←-| Patroni |←-| DCS (etcd/ | | Load Balancer | |
• (Primary/Replica)| | | | Consul) | | (HAProxy/Cloud LB) | |
• PgBouncer | | Netdata | | VIP Manager | |
• (Connection Pool)| | (Monitoring) | | | |
Component Relationships
Clearly indicate:
• Primary-replica relationships
• Load balancer distribution
• DCS communication paths
• Monitoring data collection
• Console management flow
Additional Details
Annotations for:
• Port numbers for key services
• Failover paths
• Backup flows
• Management API endpoints
• Authentication boundaries