
Sign up to save your podcasts
Or


There are many reasons to split up large-scale systems towards more modular, smaller services with their own model and language. You can decouple teams and give full autonomy of that service to a team. By decoupling services and teams you can handle changes to the domain faster, having a faster time to market. You decrease the cognitive load of the teams, empowering teams to truly understand the complexity of their shared models with domain experts.
But how do we split up large-scale systems? What are the characteristics we can dissect a bounded context? How do we split towards a microservices architecture? We do not only have to deal with shifting terminology here but also different rates of change in the business.
Join us in this Panel where we will hunt for design heuristics to split systems towards bounded contexts and microservices.
By Virtual Domain-driven designThere are many reasons to split up large-scale systems towards more modular, smaller services with their own model and language. You can decouple teams and give full autonomy of that service to a team. By decoupling services and teams you can handle changes to the domain faster, having a faster time to market. You decrease the cognitive load of the teams, empowering teams to truly understand the complexity of their shared models with domain experts.
But how do we split up large-scale systems? What are the characteristics we can dissect a bounded context? How do we split towards a microservices architecture? We do not only have to deal with shifting terminology here but also different rates of change in the business.
Join us in this Panel where we will hunt for design heuristics to split systems towards bounded contexts and microservices.

274 Listeners

287 Listeners

623 Listeners

289 Listeners

45 Listeners

38 Listeners

144 Listeners

39 Listeners

987 Listeners

188 Listeners

2,216 Listeners

14 Listeners

5,560 Listeners

73 Listeners

15,841 Listeners