Remove microservices-apache-kafka-domain-driven-design
article thumbnail

Microservices, Apache Kafka, and Domain-Driven Design

Confluent

Microservices have a symbiotic relationship with domain-driven design (DDD)—a design approach where the business domain is carefully modeled in software and evolved over time, independently of the plumbing that makes the system work. Microservices. How should microservices communicate with each other?

Kafka 109
article thumbnail

Making Sense of Real-Time Analytics on Streaming Data, Part 1: The Landscape

Rockset

Kafka or Kinesis ? This blog series will help demystify streaming data, and more specifically, provide engineering leaders a guide for incorporating streaming data into their analytics pipelines. Flexible schema : JSON allows for flexible schema design, which is useful for handling data that may change over time.

Kafka 52
Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

Putting Events in Their Place with Dynamic Routing

Confluent

Event-driven architecture means just that: It’s all about the events. In a microservices architecture, events drive microservice actions. In the most basic scenario, microservices that need to take action on a common stream of events all listen to that stream. No event, no shoes, no service. Branching an event stream.

Kafka 108
article thumbnail

Reliable Data Exchange with the Outbox Pattern and Cloudera DiM

Cloudera

In this post, I will demonstrate how to use the Cloudera Data Platform (CDP) and its streaming solutions to set up reliable data exchange in modern applications between high-scale microservices, and ensure that the internal state will stay consistent even under the highest load. Introduction Many modern application designs are event-driven.

article thumbnail

Journey to Event Driven – Part 2: Programming Models for the Event-Driven Architecture

Confluent

Part 1 of this series discussed why you need to embrace event-first thinking, while this article builds a rationale for different styles of event-driven architectures and compares and contrasts scaling, persistence and runtime models. Event-driven architecture. Event-driven, reactive architecture. Event-driven architecture.

article thumbnail

Journey to Event Driven – Part 3: The Affinity Between Events, Streams and Serverless

Confluent

What is more, as the world adopts the event-driven streaming architecture, how does it fit with serverless? When it comes to the emerging serverless world, It makes sense to validate how Apache Kafka ® fits in considering that it is mission critical in 90 percent of companies. Do they complement or compete? What is FaaS?

Kafka 109
article thumbnail

Journey to Event Driven – Part 4: Four Pillars of Event Streaming Microservices

Confluent

All of these, and more, lead to design patterns that can be used and reused. To read the other articles in this series, see: Journey to Event Driven – Part 1: Why Event-First Thinking Changes Everything. Journey to Event Driven – Part 2: Programming Models for the Event-Driven Architecture. What is the latency?

Kafka 93