Week 28, year 2021
- EventStoreDB 21.6: stability, performance, and strategic importance - June is here and, as planned, EventStore 21.6 has been shipped. It is a substantial release containing important usability, stability, performance, and fixes and features as well as being an important step towards EventStoreDB's strategic architectural vision. [Event Store blog]
- Form a wall! And other concerns about security - There were 0.3 seconds left till the end of the NBA match. Detroit Pistons were leading by a single point against San Antonio Spurs. The… [Event-Driven by Oskar Dudycz]
- How to get the current entity state from events? - In Event Sourcing, the application state is stored in events. When we add an event, it is placed at the end of a structure called an append-only log (read more in this post What if I told you that Relational Databases are in fact Event Stores?). Events are the source of truth. This has many advantages, such as: [Event Store blog]
- Sponsored Post - Pinecone, Kinsta, Bridgecrew, IP2Location, StackHawk, InterviewCamp.io, Educative, Stream, Fauna, Triplebyte [High Scalability]
- Snapshotting Strategies - Looking at resources from the Internet, you may conclude that snapshots are an essential part of the Event Sourcing system. It may be tempting to read the current state from a single record instead of multiple events. We could store it separate database in parallel to appending a business event. You cannot deny that reading a single entry is faster than reading more of them, right? [Event Store blog]
- RabbitMQ Streams Overview - A RabbitMQ stream models an append-only log with non-destructive consuming semantics. This means that – contrary to traditional queues in RabbitMQ – consuming from a stream does not remove messages. Streams in RabbitMQ are persisted and replicated. This translates to data safety and availability (in case of the loss of a node), as well as scaling (reading the same stream from different nodes.) [RabbitMQ - Blog via Aggregater Linklog]
- Domain-Driven Refactoring: Procedural Beginnings - As part of the red-green-refactor TDD process, the second step of making the test pass means we write the simplest (but still correct) code that can possibly work that flips our test from red to green. [Jimmy Bogard]
- AxonIQ Academy Frequently Asked Questions - If you were to sneak-peek into AxonIQ’s internal chat, you’d quickly notice that the following comic from xkcd.com pops up once in a while in quite a few channels. [Blog]