Microservices & Distributed Monoliths
“Microservices should contain no more than 100 lines of code” … “Microservices are REST APIs that communicate with JSON” … Where did all these microservice recommendations come from? Without a microservices game plan, you may end up with a distributed monolith, with all the worst attributes of a monolithic system and all the complexity of distributed microservices as well. You might even wonder if you should be using microservices at all.
In this session I’ll provide a roadmap to microservices that avoid the pitfalls of coupling that slide toward the pit of distributed monoliths, and introduce basic tenets of ViewModel composition that allow you to stitch data from properly segregated microservices in your UI.
Or maybe you’ll just be convinced you don’t need microservices after all.