Systems | Development | Analytics | API | Testing

Data Streaming

What is the Event Sourcing Pattern? | Designing Event-Driven Microservices

Feb 15, 2024 By Confluent In Confluent
Event Sourcing is a pattern of storing an object's state as a series of events. Each time the object is updated a new event is written to an append-only log. When the object is loaded from the database, the events are replayed in order, reapplying the necessary changes. The benefit of this approach is that it stores a full history of the object. This can be valuable for debugging, auditing, building new models, and a variety of other situations. It is also a technique that can be used to solve the dual-write problem when working with event-driven architectures.
View Video

What is the Transactional Outbox Pattern? | Designing Event-Driven Microservices

Feb 8, 2024 By Confluent In Confluent
The transactional outbox pattern leverages database transactions to update a microservice's state and an outbox table. Events in the outbox will be sent to an external messaging platform such as Apache Kafka. This technique is used to overcome the dual-write problem which occurs when you have to write data to two separate systems such as a database and Apache Kafka. The database transactions can be used to ensure atomic writes between the two tables. From there, a separate process can consume the outbox and update the external system as required.
View Video

What is the Dual Write Problem? | Designing Event-Driven Microservices

Feb 1, 2024 By Confluent In Confluent
The dual write problem occurs when you try to write to two separate systems and need them to be atomic. If one write fails, and the other succeeds, you can end up with inconsistent state. This is an easy trap to fall into, and it can be difficult to avoid. We'll explore what causes the dual-write problem and explore both valid and invalid solutions to it.
View Video

How To Build Scalable and Resilient Microservices | Microservices 101

Jan 25, 2024 By Confluent In Confluent
Building scalable and resilient microservices requires an approach that eliminates the need to treat them as special. They should be treated as easily replaceable building blocks. This means eliminating bottlenecks and single points of failure but it can also mean changing from a pull-based approach to a push-based approach. CHAPTERS.
View Video

Point-to-Point vs Publish/Subscribe | Microservices 101

Jan 19, 2024 By Confluent In Confluent
Communication between microservices can be broadly categorized as either point-to-point or publish/subscribe. Point-to-point is often used synchronously, while publish/subscribe tends to be asynchronous. Each of these techniques can have a place in a modern microservices platform, but it is important to understand the role each one plays so that they can be used effectively. CHAPTERS.
View Video
confluent

Getting Started with OAuth for Confluent Cloud Using Azure AD DS

Jan 12, 2024 By Coran Stow In Confluent

Released in December 2022, OAuth support on Confluent Cloud allows Confluent Cloud users to integrate their own third-party identity provider (IdP) with Confluent Cloud, centralizing account management across all of their cloud services. This article explains how to configure Azure Active Directory DS (Azure AD DS) and Confluent Cloud so that the Azure Directory can be used to authenticate and authorize applications to use Confluent Cloud clusters.

Read Post
Subscribe to Data Streaming

Copyright © 2024 OpsMatters™. All rights reserved.