Week 29, year 2022
- Sponsored Post - G-Core Labs, Close, Wynter, Pinecone, Kinsta, Bridgecrew, IP2Location, StackHawk, InterviewCamp.io, Educative, Stream, Fauna, Triplebyte [High Scalability]
- Advocate, educator, and authorial stance - When I'm writing, or mentoring others in writing, about a particular technique I prefer to take the role of an educator rather than that of an advocate. When doing that, I see two main stances an author can take. One is to focus on the trade-offs between this technique and its alternatives, the other is to focus on the merits of the particular technique and not discuss the alternatives. [Martin Fowler]
- How to effectively compose your business logic - Let’s say that we’d like to implement Shopping Cart. We have the following requirements: The customer may only add a product to the shopping… [Event-Driven by Oskar Dudycz]
- 21.10.6 Release Notes - We are pleased to announce the official release of EventStoreDB OSS & Commercial version 21.10.6 long term support (LTS). [Event Store blog]
- Kafka on Kubernetes: What could go wrong? - Understand the risks and rewards of data streaming with Kubernetes [Redpanda Blog via Aggregater Linklog]
- Secondary Server Nodes in Axon Server - Optimized storage for cost efficiency - Cost optimization for Axon Server deployments without sacrificing performance is very important to our customers. The most commonly used technique is the optimization of storage for the events. To cater for this optimized storage, Axon Server Enterprise Edition (ASEE) provides the concept of multi-tiered storage - a secondary server node. This capability not only helps lower storage costs but also helps retain the performance and, in some cases, actually improvising it. This technique splits the storage of events across multiple nodes within an ASEE cluster. ASEE nodes have designated roles within a cluster: Primary / Backup and Messaging-Only. ASEE introduced a new role - Secondary since version 4.4, to cater for this split (also known as multi-tier) storage requirement. By designating a node as a “Secondary” node within a cluster, the storage of events is distributed between the “Primary” and “Secondary” nodes. [Blog]