Migrate a monolithic wallet to microservices
AppleSoftware Engineer · Technical Screen
Last updated
This question evaluates a candidate's ability to design and plan a safe, compliant migration of a high-scale digital wallet from a monolithic architecture to microservices, covering service decomposition, data ownership, transactional consistency, security and key management, compliance, observability, and deployment strategies.
Assume you operate a monolithic digital wallet and peer-to-peer payments application (similar to Apple Cash). How would you migrate it to a microservices architecture? Define service boundaries (e.g., identity/KYC, wallet, ledger, payments orchestration, risk/fraud, notifications), data ownership and migration plan, API design and idempotency, cross-service transaction patterns (saga versus two-phase commit), consistency and reconciliation, authentication/authorization, PCI/PII compliance, observability, and deployment/rollout strategy (strangler pattern, canary, rollback). Provide a phased migration plan, key risks, and success metrics.
Solution walkthrough is for members
Get the full walkthrough with reference code and complexity analysis, plus Kitty Coach at 300 messages a day. Hints, the code runner and community answers stay free.