To Kill a Monolith: Slaying the Demons of a Monolith with Node.js Microservices on CloudFoundry
summary
Bluemix UI migrates from a single Java/Dojo monolith to a set of 25 Node.js microservices deployed on Cloud Foundry, using a central proxy-based routing layer to stitch pages together with server-side templating and a Redis shared session for tokens. Deployment grows to ~95 instances and 55–60 GB of RAM at peak; blue‑green releases use dual on‑deck/prod sets and proxy swaps. Monitoring (per‑request metrics, synthetic SiteSpeed.io checks) and Dyn geo load balancing enable global failover. Result: faster pages, better SEO and team autonomy, at the cost of more operational complexity.
AI-written summary · about
chapters (13)
- 0:00Introduction to monolith migration
- 3:35Demons of the monolith
- 6:05Weapons of microservices
- 12:09Phase one migration
- 13:15Phase two migration
- 15:24Demo of seamless navigation
- 16:11New challenges in microservices
- 18:40Blue-green deployments at scale
- 20:51Importance of monitoring
- 22:44Global load balancing
- 25:23Memory usage trade-offs
- 27:14Keeping regions in sync
- 30:05Tips for monolith migration
related talks
35mTo Kill a Monolith: Slaying the Demons of a Monolith with Node.js Microservices on CloudFoundry
33mMigrating the Bluemix UI to a Microservices Architecture on CloudFoundry
29mNode.js Micro-Services
30mBanking on Cloud Foundry Platform: A Case Study of Digital Business Banking Applications
12mScaling a Monolith, Is A Four-Letter Word
31mDeploying Microservice Architectures with Cloud Foundry
26mMonoliths always pay their debts
31mMigrating from Monolith to Microfrontends