To Kill a Monolith: Slaying the Demons of a Monolith with Node.js Microservices on CloudFoundry
summary
Bluemix UI migrates from a single Java monolith to Node.js microservices deployed on CloudFoundry, moving from three 2GB Java instances (~6GB) to roughly 25 core services and ~100 total apps with an estimated ~55GB memory footprint. Server-side Dust.js templating and Redis session storage improve SEO and session sharing; Akamai + DNS routes users to the nearest healthy region (four public CloudFoundry deployments). Deployments occur a few times per week, monitoring uses HTTP metrics and dashboards, and releases use Blue-green at the proxy with runtime composition and centralized health checks.
AI-written summary · about
chapters (8)
- 0:00Introduction to monolith challenges
- 1:48Problems with monolithic architecture
- 5:07Adopting microservices strategy
- 10:03Migration progress and milestones
- 15:13New challenges with microservices
- 19:33Monitoring and resilience in microservices
- 21:45Global console and load balancing
- 23:33Summary and Q&A
related talks
31mTo 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
34mSplit That Monolith: a Java on Cloud Foundry Story
29mNode.js Micro-Services
26mMigrating Enterprise Microservices From Cloud Foundry to Kubernetes
26mMonitoring Node.js Microservices on CloudFoundry with Open Source Tools and a Shoestring Budget
31mDeploying Microservice Architectures with Cloud Foundry
31mCloud Foundry and Microservices: A Mutualistic Symbiotic Relationship