How phobiavr/phober works
Main Components
• API Gateway:
• API Gateway container (located under docker/api-gateway) as the single entry point for all client requests.
• How routing is handled, with URL path prefixes (/auth, /hardware, /crm, /staff) mapping to appropriate microservices.
• Microservices:
• Service residing in the “services” folder, including adminpanel, auth-server, config-server, crm-service, device-service, notification-server, and staff-service.
• That each of these microservices is an independent module, with internal communication managed via the API Gateway.
• Shared Components:
• A component or library layer for “shared/laravel-common” that is used across multiple services.
• Media/Buckets:
• Interactions: the adminpanel for read/write access and device-service for read-only access.
• Database Containers:
• Various database instances (MySQL, Postgres, Oracle, SQLite, SQL Server) which are available as Docker containers. These might be drawn either as separate blocks or as a “Database Layer” that the services interact with.
• Docker Infrastructure:
• Supporting Tools:
• Logging/monitoring via the ELK stack (from docker/elk) if deemed critical to the overall system’s observability.
Relationships and Data Flow
• Optionally, show how shared components are imported/used by multiple microservices.
Architectural Patterns & Design Principles
• Microservices architecture pattern by clearly segregating the API Gateway, multiple backend services, and storage layers.
• Separation of concerns: the API Gateway isolates client interaction and routing, while each microservice handles domain-specific logic.
• Mention that the inter-service communication is abstracted, potentially through REST APIs, as suggested by the provided Postman collection.
• Usage of Docker Compose and containerization as a key operational pattern that supports the deployment and scalability aspects.