Architecture Decisions
Building a B2C application requires identity architecture that supports the complete customer lifecycle while protecting customer credentials and personal data.
Four decisions shape the architecture:
- Integration pattern: where identity screens live and how your application and ThunderID divide responsibility.
- Identity sources: where customer identities come from and which system owns the canonical record.
- Tokens and APIs: how sessions, tokens, permissions, and API validation work after sign-in.
- Run and observe: how your team deploys, monitors, audits, and connects the identity system.
Start with the integration pattern because it defines the boundary between your application and ThunderID. Review the supporting decisions as your application needs more control over identity data, API protection, deployment, or operations.
Supporting decisions
