Domain Driven Design Kafka Topic

Would it be good design to store all types of order event into single kafka topic and to have the orderid as the message key.

Domain driven design kafka topic. We ve standardized on apache. How developers can become great writers. Kai waehner discusses why apache kafka became the de facto standard and backbone for microservice architectures not just replacing other traditional middleware but also building the microservices themselves using domain driven design and kafka native apis like kafka streams ksqldb and kafka connect. The overflow blog podcast 268.

In our credit card example kafka would be easily able to ingest large amounts of requests being sent to the system to allow for later processing. Apache kafka is a cool product but if you are thinking about using it for event sourcing you should think again. An event driven design comes with the need for. We could design a system where hundreds of thousands of messages are being sent per second to a commands topic step 1 and then consume them at a pace that suits the business.

Kafka is a great tool for delivering messages between producers and consumers and. Domain driven design ddd concept was introduced by first eric evans in 2003. So basically ddd was introduced to solve the problem of a. In general a ddd aggregate is used to transfer state which can be comprised of multiple different domain objects that are together treated as a single unit of information.

The relation between a consumer group and a kafka topic is like a publish subscriber service where the subscriber is the entire consumer group. The concept of microservices did not exist at that time. Communication in event driven land usually happens through some kind of messaging system. Browse other questions tagged domain driven design apache kafka event sourcing or ask your own question.