Modernizing a Legacy Application with Play, Scala and Mongo DB
summary
A legacy monolithic web application is refactored into an API-centered architecture using Play Framework, Scala, Akka and ReactiveMongo so external apps no longer access the database directly. A self-contained "espace candidat" service isolates candidate-facing business logic, and a migration pipeline moves over 10 years of candidate data from SQL to MongoDB with actor-based parallel jobs and a short downtime for the final delta; integration tests run against an embedded Mongo and deployments happen weekly.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 2:08Project constraints goals
- 5:19Initial architecture
- 9:47New API architecture
- 15:01Data migration MongoDB
- 17:47Testing Play embedded MongoDB
- 23:00Modern API best practices
- 29:24Error handling maintenance
- 32:55Experience report conclusion
related talks
33mThe rise and fall of the full stack database
01h 05mMigrating to Microservice Databases: From Relational Monolith to Distributed Data
23mRe-Architecting Big Environments
43mPostgresQL as an Application Modernization
25mHybrid Applications with MongoDB and RDBMS
51mAdvanced search for your legacy application
49mAdvanced (elastic)search for your legacy application
43mCRIMS: The case of the DB change that left no trace
