Independent services
Each product and platform service can evolve and deploy through its own API and persistence layer.
TECHNICAL ARCHITECTURE
Designed for independent evolution.
Ledger uses a service-oriented .NET architecture. Product services own their operational data; shared control services handle configuration, registry, security, messaging, observability and assurance.
LEDGER SIGNALSClear boundaries make the platform extensible.This is a design and codebase overview, not a claim about every production deployment.
SYSTEM DESIGN
A control plane and a product data plane.
The codebase separates the platform framework from Ledger Business products and agent work. Contracts and events carry information between services rather than direct reads of another service's database.
Owned operational stores
A service owns its operational database. Cross-service access goes through contracts, APIs or events.
Config & registry
Central services distribute runtime configuration and describe service availability.
Messaging
Event contracts include correlation, tenant, source and schema information for traceability.
DataHub
Shared reporting, search and export use projections, leaving operational ownership with services.
Web & generated clients
The control center and products use API contracts and generated clients to reach services.
How the pieces connect
Trace a business action end to end.
A user action enters through an authenticated UI and a versioned API. The owning service validates and persists it, then publishes facts for other services and reporting projections. Correlation and audit data link the journey.
IdentityAPI contractOwning serviceEventProjection
Continue exploring
Understand the security model.
Explore the identity, permission and tenant controls around each service boundary.