PinnedInThe Yield Studio PlaybookbyJoe FRANCOIS·Feb 4, 2025DDD: How to design aggregates?Discover key tips to master aggregates: when to split them, how to build them, and make them collaborate effectively!A response icon6A response icon6
PinnedInThe Yield Studio PlaybookbyJoe FRANCOIS·Dec 8, 2024DDD: These aren’t the bounded context you’re looking forAfter yet another post titled “DDD with Framework X, the ultimate guide,” I can’t resist the urge to set the record straight.A response icon5A response icon5
PinnedInThe Yield Studio PlaybookbyJoe FRANCOIS·Dec 1, 2024DDD: Do not leak your domain eventsIt has happened to me far too often to take over projects using a DDD approach that showcased what I struggle with the most: coupling.A response icon10A response icon10
PinnedJoe FRANCOIS·Mar 30, 2021How to develop and test with Google Cloud Datastore running locally?If you’re having projects running with Google Cloud Datastore, you’ve probably wonder if it would be possible to just have the whole stack…
Joe FRANCOIS·Mar 24Event Sourcing: Projections Must Tell the Same StoryIf your events are designed to please your read models, you’ve missed something essential.
Joe FRANCOIS·Mar 17Supercharging Obsidian with AI using MCPTurning your second brain into an AI-accessible knowledge system
InThe Yield Studio PlaybookbyJoe FRANCOIS·Feb 16, 2025DDD: Should I write all the code using English?When English is not your business language, what is the best approach? Translating everything into English? Using the original business…A response icon20A response icon20
Joe FRANCOIS·Dec 7, 2024First, thanks for reading.Good question. If you do keep your domain events private, you indeed know your consumers without knowing what they can do of your events…
InThe Yield Studio PlaybookbyJoe FRANCOIS·Sep 30, 2024A simple decision to save you from one of your worst nightmaresAnother little anecdote from my life as a Senior DeveloperA response icon1A response icon1
