Please log in to watch this conference skillscast.
Using DDD for mapping a company’s core domain is quite known and one can find many case studies on that, but case studies for merging or re-dividing domains upon acquisition are harder to find.
As an R&D director at Taboola, Ora had the opportunity of leading a technical due-diligence of an acquired company. During that time Taboola considered a few alternatives of how such an acquisition might look like from two main perspectives: organization structure and technical integration whereas the two obviously affect each other per Conway’s Law.
In addition, post acquisition previous assumptions turned out to be inaccurate and required further domain analysis, for finding a better solution.
During those challenging times, Ora found DDD to be a very practical tool for executing the relevant change.
If you are in a dynamic company where teams, products and domains grow fast and then split or merge, you need to constantly analyze the domains and consider alternatives for those changes. From his experience, DDD approach helps visualizing and considering these alternatives while being able to keep the discussion both business and technical.
In this talk, Ora will share the two years journey post acquisition. A journey in which domains merged and split due to a dynamic environment, for example: -Why they used DDD to decide an acquired team should stay as an isolated domain, acting as a supportive domain in the company -How they later merged part of a supportive domain into the core domain -How and why they ended up splitting the merged domain again
YOU MAY ALSO LIKE:
Oops, I DDD it Again (and Again)
With 15 years of experience in designing architecture and leading groups, Ora’s passion lies in the connection of building an architecture that empowers and motivates teams to take e2e ownership on products.