Architecture¶
Deep dive into VoIPBIN’s internal architecture, microservices, communication patterns, and deployment.
Note
AI Context
This section provides comprehensive documentation of VoIPBIN’s system internals. Relevant when an AI agent needs to understand how the platform is built, how services communicate, or how infrastructure is deployed. For API usage, see the individual resource documentation pages.
Note
AI Implementation Hint
VoIPBIN uses RabbitMQ RPC for all inter-service communication, not HTTP. When making API calls, use https://api.voipbin.net/v1.0/ as the base URL. The API gateway (bin-api-manager) handles authentication and routes requests internally via RabbitMQ to the appropriate backend service.
- Overview
- Backend Microservices
- Microservices Organization
- Service Characteristics
- API Gateway - bin-api-manager
- Special Service Architectures
- Service Independence
- Service Communication Patterns
- Service Discovery and Configuration
- Health Monitoring
- Error Handling and Resilience
- Deployment Architecture
- Monitoring and Observability
- Best Practices
- Inter-Service Communication
- Data Architecture
- Data Flow Diagrams
- Real-Time Communication (RTC)
- System Request Flows
- Request Flow Overview
- Flow 1: Create Call (Simple)
- Flow 2: Get Call with Caching
- Flow 3: Call with Event Broadcasting
- Flow 4: Complex Multi-Service Flow
- Flow 5: Real-Time Event Notification
- Flow 6: Error Handling Flow
- Performance Optimization
- Best Practices for Developers
- Debugging Request Flows
- Summary
- Call Flow Sequences
- Deployment Architecture
- Security Architecture