From Monolithic Monster to Majestic Microservice App
summary
A messy .NET monolith that fails to build and required three weeks of merging becomes a set of incremental services: authentication (IdentityServer + JWT) split into auth/profiles/users, logging moved off the main DB, and an alert service for email/SMS. The team uses Azure Functions triggered from an Azure Service Bus, fronted by API Management Gateway, and replaces mobile clients with Xamarin. The strangler pattern drives gradual cutover; cold starts, consumption-plan wakeups and schema drift bite, but production rollout to NHS hospitals succeeds under a tight deadline.
AI-written summary · about
chapters (10)
- 0:00Introduction and speaker intro
- 11:19Inheriting the monolithic monster
- 14:11Introducing the strangler pattern
- 19:13Choosing microservices architecture
- 21:46Using Azure Functions for new services
- 27:57Implementing API gateway
- 32:34Key lessons and achievements
- 34:20Team process and challenges
- 39:45Resources and closing remarks
- 40:07Q&A session
related talks
48mMicroMonolith
23mOn the road from Monolith to Micro
36mDo Proper Monoliths before You Do Microservices!
20mMonolith Thick Client Apps to Microservices! Best Practices
42mDo proper monoliths before you do microservices!
54mFrom a distributed monolith to a microservices solution
10mMicroservices, Messaging, and Failure: How Simplifying Our Architecture Saved Us
45mUsing modern .NET technologies to decompose a monolith into micro-services