Services And Data
This page maps the service landscape shown in the Alpha Looms architecture to the main data and infrastructure dependencies visible in the current deployment diagram.
Service Landscape
The diagram shows a platform built from multiple service groups rather than a single application runtime.
Frontend, Gateway, And Platform Services
Admin WebBorrower WebSales WebSales AppFormioAdmin API GatewayBorrower API GatewayOpenAPI API GatewayN8NSupabaseSupersetKeycloak
Downstream Services
The runtime also includes multiple downstream domain and operational services behind the gateway layer.
This documentation avoids enumerating every microservice individually. Where useful, the architecture highlights a few recognizable examples such as Auth, Log management, and beta-related services.
Service Grouping By Backing Platform
The diagram visually groups some services by the databases or platforms they depend on.
Supabase-Associated Capabilities
Inside the Supabase DB area, the diagram groups workflow, state, and platform-management capabilities.
This suggests a shared operational data plane for stateful workflow and platform-management concerns.
MySQL-Associated Downstreams
Inside the MySQL DB area, the diagram groups core lending, auth, and related servicing domains.
These downstreams align with the main business and operational flows of the platform.
PostgreSQL-Associated Downstreams
Inside the PostgreSQL DB area, the diagram groups document and log-management related services.
This indicates a separate operational storage pattern for document and logging-related concerns.
Additional Dependencies
The architecture also shows several managed dependencies attached to different services.
Messaging And Integration
Service Busfor asynchronous or event-driven integration paths
Caching And Operational Storage
RedisMongoDB
Blob And Account Storage
betateststorageauthalphatest01
These components are important when planning service interactions, state handling, and non-relational data flows.
Beta Service Area
The beta service cluster includes beta-focused downstreams and supporting compute integrations.
The diagram also shows supporting storage and MongoDB connectivity in this area, indicating a specialized runtime path separate from the main lending-service grouping.
API Catalog
Use the API Catalog for contract details such as request models, response schemas, and endpoint behavior.
Reading The Architecture Correctly
Use the architecture as a runtime and dependency map, not as a promise that every component is directly exposed for external integration.
When assessing an integration, distinguish between:
- components that are part of the deployment topology
- components that are reachable through documented APIs
- components that are internal operational dependencies only