David Boike is a Solution Architect at Particular Software, the makers of the NServiceBus platform, and the author of Learning NServiceBus, Second Edition. He is also a husband, father of two, craft beer homebrewer, and all-around nerd.
We’ll understand service oriented architecture concepts, and DDD concepts such as bounded contexts and data ownership. We’ll apply those concepts to build a simple, yet fully functional, order management system. Read more...
“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.
Author of “Domain-Driven Design”
Discerner of the Code
Inventor of EventStorming
Serial DDD Advocate
Web App Developer & Designer
Distributed Systems and Stuff
Event-Driven Model Enthusiast
Creator of Axon Framework
Student of Systems
Strategic Design Specialist
Emerging Human, Recovering Engineer
Better by Design, Excel by Build
Use Case Driven
Organiser of KanDDDinsky
Principal Software Engineer