Monolith Thick Client Apps to Microservices! Best Practices
summary
Refactors a WPF monolith into hot-pluggable GUI modules using MEF framework, deploying new components from AWS via REST and an API gateway while retaining low-level drivers on-device; follows the strangler pattern and implements custom header versioning so clients download compatible bundles. Cloud license manager controls entitlements (no field activations), catalog manager stores SHA-256 checksums and dependency graphs with backup/rollback on failure, TLS 1.2 protects transit, trace IDs and a log aggregator enable end-to-end tracing, and CI/CD uses TestComplete/AQTime/Jifer.
AI-written summary · about
chapters (13)
- 0:00Introduction to migration
- 1:16Monolith drawbacks explained
- 2:42Application use case details
- 3:46Migration strategy overview
- 4:51GUI modularization with MEF
- 6:59Cloud component provisioning
- 9:11Component versioning approach
- 10:57Feature entitlement management
- 12:02Component consistency checks
- 13:05Data security measures
- 14:07Logging and tracing system
- 15:32DevOps tools and practices
- 17:42Key takeaways summary
related talks
46mFrom Monolithic Monster to Majestic Microservice App
08mWhy we are writing a monolith, not a microservice
36mDo Proper Monoliths before You Do Microservices!
57mSplitting Monolith Application to Microservices
48mMicroMonolith
30mMonolith-ifying perfectly good microservices
42mChopping the Monolith
31mMonolith to Microservices: A Guide to Seamless Transitions