Hands-On Domain-Driven Design with .NET Core [book] Alexey Zimarev. Solve complex business problems by understanding users better, finding the right problem to solve, and building lean event-driven systems to give your customers what they really want
Should We Create a Shared Service? A Decision-making Checklist [blog] Nick Tune. Deciding when to create a shared service can be highly subjective and quite often highly controversial. But there are a series of heuristics, or questions we can ask ourselves, to improve our chances of making the right sociotechnical design decision.
The Dark Side of Events [video] Vladik Khononov. Events are your industry’s near and dear. All technological conferences are full of talks on event sourcing, event driven architectures, or event driven integrations. So hey, why not make another one? …But a bit different: Let’s talk about the dark side of this pattern. Events, as any tool, can be used productively or destructively.
Local-first software: You own your data, in spite of the cloud [whitepaper] Martin Kleppmann, Adam Wiggins, Peter van Hardenberg, Mark McGranaghan. In this article we propose “local-first software”: a set of principles for software that enables both collaboration and ownership for users. Local-first ideals include the ability to work offline and collaborate across multiple devices, while also improving the security, privacy, long-term preservation, and user control of data.
Models as a Tool for Deeper Insight [blog] Dan Bergh Johnsson, Daniel Deogun, Daniel Sawano. This article delves into DDD and models: what they are, how they relate, and how models work within Domain-Driven Design.
Snicket [github] Jeff Hansen. Stream Store based on Postgres for NodeJS.
Our not-so-magic journey scaling low latency, multi-region services on AWS [blog] Jackson Moes. Engineering stateless, high-availability cloud services comes with juuuuuuust a few challenges. Here’s how we (eventually) slayed the dragon.
Domain-Driven Design: The First 15 Years [book] DDD Europe. Fifteen years after the publication of “Domain-Driven Design: Tackling Complexity in the Heart of Software” by Eric Evans, DDD is gaining more adoption than ever. To celebrate the anniversary, we’ve asked prominent authors in the software design world to contribute old and new essays.
Eventual Consistency for Mere Mortals [blog] Ralf Westphal. You’re used to merge conflicts in Git; you’re of course trying to avoid them – but in the end they happen. Then somebody will resolve them manually. That’s frustrating, but inevitable, if you want to reap the benefits of Git. The possibility of inconsistencies does not drive you away from it. Accepting eventual consistency has turned out to be very useful and has “conquered the world” of VCS.
Oops, I DDD it Again (and Again) [video] Ora Egozi-Barzilai. 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