The event driven foundation requires more wiring and boilerplate, but when the basics are in place everything is very simple to reason about. As the domain complexity increases, the architectural complexity does not.

@regisn.bsky.social heya!!

Choosing the message key(s) for your Kafka streaming application design is an extremely important decision. Kafka's promises depend on partition, and partition depends on key. Partition (key) is the unit of horizontal scaling, yet it is defined in the application domain. Is this infra or app? Yes.

CloudEvents protocol binding with Kafka, binary mode with schema registry. No need to invent message metadata scheme, adopt the standard and gain interoperability with many brokers and frameworks. Awesome.

Learning about the @axoniq.bsky.social platform architecture, it seems there's been some convergent evolution with my DDD Event Sourcing and CQRS journey. My emerging solution to this set of challenges and opportunities on paper is very similar to theirs. If we're both right, this is a good sign!

Moving envelope metadata from the message body to the message header allows the body schema to be reserved for purely domain-relevant fields.

It seems obvious now but I realized the Kafka message is already an envelope, with metadata on the outside and payload on the inside. (1/2)

The energy of a great product manager gives me hope for the cause.

Serendipity.

Event driven architecture with event sourcing on Kafka. Domain driven design.. bounded domains, entities, and aggregates to align the software architecture with the shape of the business. CQRS discipline to separate write model processing concerns from read model query optimization concerns. (1/3)

Relevant. infosecwriteups.com/devsecops-be...

I'm here to be counted.