The Journey of a strongly coupled Monolith into the Cloud Land
summary
Three-year migration of a 1M-line Java monolith moves databases and apps to AWS with Oracle → PostgreSQL conversions, 57M rows plus 8 TB blobs moved to S3, and 128 VMs replaced by Kubernetes on an internal developer platform. CI/CD shifts from Jenkins to GitLab CI, Terraform provisions infra, Kafka and Aurora appear for messaging and storage, and Elastic APM centralizes monitoring. Regulatory outsourcing (BaFin) and eventual consistency between DB metadata and S3 objects create the biggest surprises.
AI-written summary · about
chapters (10)
- 0:00Introduction and speakers
- 2:57About the company and project
- 6:09Planning the migration journey
- 8:14System context and environment
- 16:57Preparation and proof of concepts
- 21:54Creating the roadmap
- 26:27Execution of the migration
- 37:02Identity and access management
- 39:51CI/CD pipeline migration
- 44:06Finalizing and concluding the migration
related talks
31mA Journey of Migrating Data Platform from Data Center to Cloud
58mJourney to the Cloud - a Rearchitecting Story
21mAvoiding That $1M Dollar AWS Bill - Mark Michael, Glenn Oppegard
23mCCC Intelligent Solutions Achieves Improved Efficiency with Oracle to AWS PostgreSQL
18mMigrating Legacy Financial Systems to Cloud: Challenges and Best Practices
22mFireside Chat with AWS
27mMigrating a Monolith to the Cloud
54mMigrating to Cloud Native with Microservices