💡 Relational databases are not losing data. They're strong, consistent and secure! Are they? Too often, we mix technical and logical concepts. Business transactions are not the same as database transactions. The fact that we can safely assume that information that we put into the database will be stored durable doesn't mean that it won't be lost. We don't even need to delete any data to lose precious business information. Each override replacing the previous state with the new one, may already erase the valuable information. For instance, seeing that the shopping cart is empty, how will you know that it's just a new shopping cart or someone added and removed a product? Such "pessimistic" scenarios are sometimes more valuable insight for the business than just knowing that everything went right and someone bought something eventually. In this example, knowing that someone put the product into the shopping cart but decided not to buy it can give us information about some gap or even an opportunity to "close the deal". Yet, we need to have that information! #EventSourcing, contrary to the standard approach, keeps all the facts that happened in our system. We can look back, and make analyses and enhanced diagnostics. Events are a great source and input for future workflows: analytics, reporting or even machine learning. Yesterday I got to speak yesterday about that during the Wrocław #Java User Group. I brought not only theory but also got my hands dirty to elbows in code using new goodies from Java. People seemed interested; there were a lot of good discussions and questions, which is the best sign for me that it was intriguing. And that's the typical pattern I see. #EventSourcing is still a niche, but it's emerging quickly into a commodity. Don't wait to jump on the bandwagon; some empty seats are still left! 😅
Oskar Dudycz’s Post
More Relevant Posts
-
I just updated my #EventSourcing self-paced kit for .NET. You don't know what's that? I have a bit of a philanthropic rule: whatever code I do for my paid workshops, I'm open-sourcing it. All backing exercises for my workshops are available for free, and you can try to do them on your own. They all have tests that will tell you if you made them well, plus some recommended solutions. It's not the same experience as the workshop, as I'm using it more for illustration and triggering discussion, or "feeling the pain". Still, I think that's a decent way to start. If you'd like to have a full experience, check my training page and contact me: https://lnkd.in/dbvAqkSz The recent update makes the learning experience more gradual. Now you can step by step learn how to use event stores like Marten and Event Store, then how to compose business logic and build a real WebAPI connecting all the dots. I already made it for Node.js: https://lnkd.in/dcG9kCia Today, I published an update for .NET: https://lnkd.in/dtJ8BWHz Java are close but not fully aligned yet: https://lnkd.in/eVKxAMnJ Sharing is caring, so I'll appreciate if you reshare it to your friends, as it cost me a lot of work and iterations, to provide all of that for free 🙂 p.s. If you're at Techorama or Domain-Driven Design Europe this year, you can try to join my workshops, I'm not 100% sure, but I think that there are still places left. More info here: https://lnkd.in/daSUZyvR
-
-
#Testcontainers became a popular way of setting up dependencies for integration testing. They're not ideal, as configuring them to run your tests efficiently is not as trivial as it's glossed; I explained that in "A simple way to configure the integration tests pipeline" (https://lnkd.in/dv8wsNZC). Still, undeniably, it can speed up the initial ramp-up phase and, if used wisely, can be a decent way to handle common testing dependencies. Testcontainers already provide the default configurations for tools like PostgreSQL, Kafka, MongoDB etc. Yet, sometimes you need to use something a bit less mainstream, for instance, Event Store as your event store. How to do it? I explained that in my latest article, read more in: https://lnkd.in/dK3Q8YSv What other non-default containers did you configure in your project?
-
How do you make predictions about tech without the magical crystal ball? We did that today by example in the latest #ArchitectureWeekly. We analysed what Redis and Terraform license changes relate to the new Typescript framework Effect Ts and put it into the context of strangling legacy design. We also discussed the product and company culture on the Google example. Last but not least we did a sanity check on the Passkeys, if they're really the-latest-the-greatest. Plus, more stuff to boost your design skills!
Architecture Weekly #177 - 29nd April 2024
Oskar Dudycz on LinkedIn
Programista .Net w Gotoma
1yuntil some intern drops table or DB :D