Migrating the Bluemix UI to a Microservices Architecture on CloudFoundry
summary
Migrating a Dojo-based single‑page Bluemix UI off a Java monolith into per-page services on CloudFoundry, with a proxy layer serving friendly URLs (e.g. bluemix.net/solutions) and a common microservice that returns header/footer HTML so heterogeneous stacks share UI chrome. Solutions and Home are already live behind the proxy while Dashboard remains monolithic. Deployment uses a blue/green deploy pattern; work is successful but uncovers needs for context path routing, private app routing, service registry, logging/correlation IDs and composite app monitoring.
AI-written summary · about
chapters (6)
- 0:00Introduction and background
- 3:14Challenges with monolith
- 8:14Microservices migration approach
- 10:01Demo of new architecture
- 13:58Enhancing Cloud Foundry
- 28:22Q&A and closing thoughts
related talks
31mTo Kill a Monolith: Slaying the Demons of a Monolith with Node.js Microservices on CloudFoundry
35mTo Kill a Monolith: Slaying the Demons of a Monolith with Node.js Microservices on CloudFoundry
30mBanking on Cloud Foundry Platform: A Case Study of Digital Business Banking Applications
29mNode.js Micro-Services
18mMicroservices Out In the Wild
57mMigrating from a monolith to a new service
26mMigrating Enterprise Microservices From Cloud Foundry to Kubernetes
31mMigrating from Monolith to Microfrontends
