This pattern is crazy, or I'm an idiot - Learning Domain-Driven Design by Vlad K [28:56-30:38]

to book in the database, but it's like, you know, you're trying to modify the database, but the data is corrupted or it's an improper right or something like that, then it will reject both the database right and the outbox, you know, the domain model update and the outbox update. And what that also gives you is, you know, basically the reverse, right, which is you can know, okay, if this has been written to the database and is now kind of recorded as the truth, I can also have confidence that the event will be admitted, right? And that's another thing you get with the outbox pattern is like, as you're pulling this outbox, you can mark the event rows in it as published, right? And so, if you're having trouble emitting an event, it gives you some kind of like baked in retry capabilities rather than your events being super-ephemeral, which is very easy to do if you're building an event driven architecture. Right. Yeah, and these are the way that he digs into these examples and stuff. Again, super valuable, really enjoyed the section of the book. He also talks about Saga's, which Saga's are also talked about in software architecture, the hard parts. Yeah, yeah. You know, his focus is a bit more on processes, like, you know, using choreography versus coordination, and these other pitfalls that can come in. I think that software architecture, the hard parts gets a little more in depth in these topics. And so, they complement each other, but it's nice to see how Saga's fit into a DDD sort of focused book as well. Right, right.