Service Topology Overview
The MATIH Platform comprises 24 microservices distributed across two planes and seven Kubernetes namespaces. This section maps the complete service topology, including service discovery, dependency graphs, communication patterns, and failure propagation analysis.
Topology Layers
| Layer | Services | Communication |
|---|---|---|
| External Edge | Browser, CLI clients | HTTPS to Kong Gateway |
| Control Plane Mesh | 10 Java/Spring Boot services | REST + Kafka |
| Data Plane Mesh | 14 polyglot services | REST + Kafka + Redis Pub/Sub |
Sections
| Section | Description |
|---|---|
| Service Registry | Service discovery, DNS names, and configuration |
| Communication Patterns | REST, Kafka, Redis Pub/Sub, gRPC patterns |
| Dependency Map | Full dependency graph and failure analysis |
Service Count
| Metric | Value |
|---|---|
| Total microservices | 24 |
| Control Plane services | 10 (all Java/Spring Boot 3.2) |
| Data Plane services | 14 (Java, Python, Node.js) |
| Frontend applications | 8 (React/Vite) |
| Kubernetes namespaces | 7 |
| Data store technologies | 9 |
Critical Path
The following services are on the critical path for the "Intent to Insights" workflow:
api-gateway --> iam-service --> ai-service --> query-engine --> Trino
|
+--> semantic-layer
+--> catalog-serviceA failure in any of these services disrupts the primary user experience. These services are deployed with 3 replicas in production.
Related Sections
- Control Plane -- Detailed Control Plane service descriptions
- Data Plane -- Detailed Data Plane service descriptions
- Event-Driven Architecture -- Asynchronous communication patterns