[Panel] Splitting systems towards bounded contexts and microservices

Virtual Domain-driven design

Contenido proporcionado por Virtual Domain-driven design and Virtual domain-driven design. Todo el contenido del podcast, incluidos episodios, gráficos y descripciones de podcast, lo carga y proporciona directamente Virtual Domain-driven design and Virtual domain-driven design o su socio de plataforma de podcast. Si cree que alguien está utilizando su trabajo protegido por derechos de autor sin su permiso, puede seguir el proceso descrito aquí https://es.player.fm/legal.

4+ y ago 1:57:16

MP3•Episodio en casa

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.

52 episodios

#Science #Tech #Social Sciences #Domaindriven Design If #Virtual Domaindriven Design If