Tomasz Ducin
Software Developer, Architect, Consultant, Trainer. Expert in Frontend Technologies and Software Architecture. Co-creator ANF (architekturanafroncie.pl). Frontend & backend. Ex-theatre actor.
Drawing Semantic Boundaries in Business Applications (Strategic DDD in practice)
Many teams organize their software around data structures and entities, assuming that their data(base) models naturally define the right boundaries for their modules. This data-focused way of thinking often leads to fragile architectures and modularization that don’t match how the business actually evolves. As a result, teams skip the important step of Strategic Design and jump straight into technical solutions, which causes their systems to become difficult to change and grow over time.
To create software that can adapt and last, we need to move away from data-oriented approach (designing system around nouns, data normalization, no redundancy etc) and instead define boundaries based on Business Capabilities, Business Processes and Domain Archetypes.
In this talk, we’ll see the above, illustrated within the logistics domain, using practical examples to clear up common misunderstandings and show why strategic DDD is key for building better software.
Software Developer, Architect, Consultant, Trainer. Expert in Frontend Technologies and Software Architecture. Co-creator ANF (architekturanafroncie.pl). Frontend & backend. Ex-theatre actor.
Drawing Semantic Boundaries in Business Applications (Strategic DDD in practice)
Many teams organize their software around data structures and entities, assuming that their data(base) models naturally define the right boundaries for their modules. This data-focused way of thinking often leads to fragile architectures and modularization that don’t match how the business actually evolves. As a result, teams skip the important step of Strategic Design and jump straight into technical solutions, which causes their systems to become difficult to change and grow over time.
To create software that can adapt and last, we need to move away from data-oriented approach (designing system around nouns, data normalization, no redundancy etc) and instead define boundaries based on Business Capabilities, Business Processes and Domain Archetypes.
In this talk, we’ll see the above, illustrated within the logistics domain, using practical examples to clear up common misunderstandings and show why strategic DDD is key for building better software.