Monolithic to Microservices Migration

You are the lead architect for JP Morgan’s retail-banking platform. The current system is a 12-year-old Java EE monolith (≈3 M LOC) that handles everything from customer onboarding and KYC, account ledger updates, card payments, rewards, notifications, and regulatory reporting. It is deployed as a single EAR on WebLogic with one 30 TB Oracle RAC database, peaks at 12 k rps, must stay available 24×5.5 (trading-week plus Sunday batch), and is proving impossible to scale horizontally or ship features faster than one quarterly release. Your task is to design a phased, zero-downtime migration strategy that moves the platform to an event-driven microservices architecture on AWS/EKS while continuing to process live transactions. You must (1) identify the first three services to carve out and their bounded contexts, (2) explain how you will keep the monolith and new services data-consistent during dual-run, (3) describe the strangler-fig routing layer and rollback plan for every release, (4) show how you will split the shared Oracle schema into service-owned databases without breaking foreign-key integrity, and (5) detail observability, security, and compliance controls that satisfy SOX and FedLine security requirements. You have 45 min: walk the interviewers through your end-state target architecture, the 18-month roadmap, and the very first sprint that proves the pattern.