Skip to content

Details

Microservices often fail to deliver the expected benefits—not because of technology, but because service boundaries are drawn arbitrarily. In this talk, we explore how Domain-Driven Design (DDD) helps define bounded contexts and turn them into true architectural quanta: independently deployable, highly cohesive units.
We’ll walk from problem definition to domain modeling, show how to place the model at the center of each bounded context, and explain how those contexts naturally become architectural quanta. From there, we can make informed decisions about implementation—whether as modules, microservices, or serverless components such as AWS Lambda.
This talk is for software architects and developers looking for practical guidance on defining the right boundaries in their systems.

Related topics

Events in Split, HR
Software Architecture
Software Product Management
Domain Driven Design
Software Development
Software Modeling

You may also like