Customer and identity
How customer profiles and authentication are separated across Customer Management and Identity Provider systems.
CustomerCustomerDomainv1.0.0The Customer domain owns who our customers are — how they register, how their profile is maintained, and how they are au...Ownercustomer-platformMapView docs owns customer profile data and customer authentication. The catalog separates profile management from identity management so customer details and credentials have different operational boundaries.
System context map
Customer Management System
Customer Management SystemCustomer Management SystemSystemv1.0.0Internal system that is the source of truth for customer profile data. Owns the customer database and publishes customer...Ownercustomer-platformMapView docs owns Customer DatabaseCustomer DatabaseContainerv1.0.0
PostgreSQL database that is the system of record for all customer profile data.Ownercustomer-platformMapView docs. Customer APICustomer APIServicev1.0.0
The public-facing API for customer profiles. Handles commands to register and update customers, serves customer reads, a...Publishescustomer-registered, customer-updatedSubscribesregister-customer, update-customer +1APIsOpenAPIOwnercustomer-platformMapRepoView docs handles:
- Register CustomerRegister CustomerCommandv1.0.0Command to register a new customer. Ownercustomer-platformSchemaMapView docs
- Update CustomerUpdate CustomerCommandv1.0.0Command to update an existing customer's profile. Ownercustomer-platformSchemaMapView docs
- Get CustomerGet CustomerQueryv1.0.0Query to fetch a single customer by their identifier. Ownercustomer-platformSchemaMapView docs
It publishes Customer RegisteredCustomer RegisteredEventv1.0.0Published when a new customer has registered. Ownercustomer-platformSchemaMapView docs and Customer UpdatedCustomer UpdatedEventv1.0.0Published when an existing customer's profile has changed. Ownercustomer-platformSchemaMapView docs so other capabilities can react to profile changes.
Identity Provider
Identity ProviderIdentity ProviderSystemv1.0.0The identity system that authenticates customers. It is the source of truth for credentials and login, verifies sign-in ...Ownercustomer-platformMapView docs owns authentication state in User DirectoryUser DirectoryContainerv1.0.0The directory of customer credentials and identities — the source of truth for authentication.Ownercustomer-platformMapView docs. OAuth APIOAuth APIServicev1.0.0OAuth-style authentication API for the Identity Provider. Verifies customer credentials and publishes an event when a cu...Publishescustomer-authenticatedSubscribesauthenticate-customerOwnercustomer-platformMapRepoView docs handles Authenticate CustomerAuthenticate CustomerCommandv1.0.0Command to authenticate a customer with their credentials.
Ownercustomer-platformSchemaMapView docs and emits Customer AuthenticatedCustomer AuthenticatedEventv1.0.0Published when a customer has successfully authenticated.
Ownercustomer-platformSchemaMapView docs.
Integration guidance
Services that need customer profile details should use Get CustomerGet CustomerQueryv1.0.0Query to fetch a single customer by their identifier. Ownercustomer-platformSchemaMapView docs or consume customer events where a local read model is appropriate. Services that need authentication should integrate with the identity boundary, not the profile database.
This split prevents order, review and payment systems from accidentally depending on credential storage.