Skip to content

Latest commit

 

History

History
35 lines (23 loc) · 1.5 KB

Identity and Profile.md

File metadata and controls

35 lines (23 loc) · 1.5 KB

Identity and Profile

image

Capability rationale and description

Identity services are essential if we customers are to subscribe to meals, receive personal notifications, receive identity tokens, and order personalized meals and meal plans. Customer profiles will store dietary preferences, and health data that the experts could use to provide personal customer advice. At the very detailed level this would also require Encryption capability at the infrastructure level for encrypting highly sensitive data like PII or personal data highly sensitive data. Encryption capability will als manage re-encryptions and key rotations periodically.

Use cases

  • Purchase session queries customer identity from Identity Service to verify if the customer has a meal waiting for him in the fridge.
  • Purchase session queries customer identity from Identity Service to query customer credits.
  • Applications authenticate the customer via Identity Service.
  • Notifications Scheduler gets customer contact details and notification preferences.
  • Referrals and Rewards engine updates customer credits.

Components

  • Identity Service API. Accessed for Identity Management and authentication using user credentials.
  • Customer Accounts API pro vides customer profile and settings.
  • User Identities DB.
  • Customer accounts DB.

Architectural characteristics

  • Availability.
  • Fault tolerance.
  • Performance.
  • Elasticity.
  • Security

Architectural choice

  • Microservices