This site uses cookies to improve your experience. To help us insure we adhere to various privacy regulations, please select your country/region of residence. If you do not select a country, we will assume you are from the United States. Select your Cookie Settings or view our Privacy Policy and Terms of Use.
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Used for the proper function of the website
Used for monitoring website traffic and interactions
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Strictly Necessary: Used for the proper function of the website
Performance/Analytics: Used for monitoring website traffic and interactions
This is the question I get asked the most, so I’ve put together this article describing a workshop recipe you can use. In Domain-Driven Design, a large system is decomposed into bounded contexts , which become natural boundaries in code as microservices and as teams in the organisation. 1 hour) Candidate Context Modelling (min.
If you would like to learn or practice how to break up a large business into domains and use them as the foundation for your softwarearchitecture and team organization, I have created a strategic domain-driven design kata that you may find useful. Design review is basically a code review but for architecture.
There are a few qualities that differentiate average from high performing software engineering organisations. I believe that attitude towards the design of code and architecture is one of them. The same mindset should also be applied to architecture; involve the whole team and challenge the small details.
In every workshop, I always ask everyone “Imagine there is no text here. What do you read from the image below, and what might you propose to do next in the workshop? You can do this with almost any visual workshop technique. What is this arrangement of colours and shapes telling you?”.
This organisational pattern can be mirrored in the softwarearchitecture, emphasising the sociotechnical nature of systems. While it is nice to go out of your way to please others, the resulting compromises to the softwarearchitecture can lead to dangerous sociotechnical side-effects.
We will be running a remote-optimised domain-driven design workshop on 15–16th June where we will use some of the techniques discussed in this post and many others, like the bounded context canvas. We can use these to capture outcomes from the workshop aka follow-up actions. In my in-person workshops, I’ve faced this hard limitation.
One of the challenges I see regularly is inertia following domain discovery workshops. In companies with many teams and many millions of lines of code, including a lot of legacy, there are endless things that can be improved in the product, software, and organization. Why Thing Get Stuck After Discovery?
Lack of accountability leads to unmaintainable software that grows harder and harder to change. As our legacy systems become less maintainable the negative spiral begins: the code is hard to evolve, nobody enjoys working on it, features take ages to deliver, politics ramp up….
In software, reacting to unforeseen circumstances in real-time is not possible. We have to specify with great precision in code exactly what our business rules are, and the computer will apply them exactly as we tell it to. But there is a problem? Hope to see you there.
Loosely-coupled teams enabled by loosely-coupled softwarearchitecture is one of the strongest predictors of continuous delivery performance and organizational scaling. Whenever a team starts on a piece of work they should own all of the code and infrastructure that needs to change in order to deliver the work.
We organize all of the trending information in your field so you don't have to. Join 5,000+ users and stay up to date on the latest articles your peers are reading.
You know about us, now we want to get to know you!
Let's personalize your content
Let's get even more personalized
We recognize your account from another site in our network, please click 'Send Email' below to continue with verifying your account and setting a password.
Let's personalize your content