Architecture
Polyglot Systems Lab HLD: see the component list below
Components and connections (9 / 16)
- Client / Consumer (Client): Calls the system through a stable public contract.
- Shared Contracts (Component): Versioned API/event schemas and compatibility rules rather than shared implementation code.
- Delivery Pipeline (Process): Runtime-specific builds behind one release policy and shared quality gates.
- Edge / API Gateway (Network): Routing, auth boundary, request correlation and policy enforcement.
- TypeScript Service (Service): Product-facing orchestration and fast-evolving application workflows.
- Go Service (Service): Runtime boundary intended for concurrency-heavy or resource-sensitive workloads.
- Java Service (Service): Runtime boundary intended for mature domain/service ecosystems and JVM tooling.
- Event Backbone (Queue): Asynchronous integration boundary for decoupled workflows and replayable state transitions.
- Unified Telemetry (Service): Trace IDs, metrics, logs and service-level signals expressed consistently across runtimes.
- Client / Consumer to Edge / API Gateway: HTTPS
- Edge / API Gateway to TypeScript Service: routes
- Edge / API Gateway to Go Service: routes
- Edge / API Gateway to Java Service: routes
- Shared Contracts to TypeScript Service: governs
- Shared Contracts to Go Service: governs
- Shared Contracts to Java Service: governs
- TypeScript Service to Event Backbone: publishes/consumes
- Go Service to Event Backbone: publishes/consumes
- Java Service to Event Backbone: publishes/consumes
- TypeScript Service to Unified Telemetry: emits
- Go Service to Unified Telemetry: emits
- Java Service to Unified Telemetry: emits
- Delivery Pipeline to TypeScript Service: builds/deploys
- Delivery Pipeline to Go Service: builds/deploys
- Delivery Pipeline to Java Service: builds/deploys
Aspirational/conceptual. YAML calls it an evolving workspace; no repo or evidence referenced.