Hila Fox
1 min readJun 2, 2023

--

Hi Vaughn, the thoughts behind this were that possibly if we find a team growing too much we might have modeled the bounded context incorrectly. Not necessarily that we would separate only due to a technicality that is a team growing but we see this as an opportunity to ask ourselves if we got it wrong and It does happen from time to time because no one is perfect. Hope this clears up the thoughts around this, I am assuming that in the post it might have not been clear.

Actually, thinking about this now, in the two years of us using these patterns in our designs there has been only two cases in which a team chose to use the bounded context pattern and both were around really new domains. This also makes me think that if it's a new domain the possibility of getting it wrong is a bit higher.

Hope this makes sense, let me know if you have any more thoughts around this

Sign up to discover human stories that deepen your understanding of the world.

Free

Distraction-free reading. No ads.

Organize your knowledge with lists and highlights.

Tell your story. Find your audience.

Membership

Read member-only stories

Support writers you read most

Earn money for your writing

Listen to audio narrations

Read offline with the Medium app

--

--

Hila Fox
Hila Fox

Written by Hila Fox

Staff Engineer @ Forter. An experienced staff+ engineer with over 10 years of experience. #scale #distributed_systems #domain_driven_design

No responses yet

Write a response