The ownership point is the one most teams skip. A topic without a named owner and a versioned schema becomes a dumping ground, and consumers fail silently when a producer changes a field. In event-driven work I have seen, the schema registry and the event contract matter more than the broker choice.
Pub/Sub Isn't Event-Driven Architecture: Here's What Most Teams Miss
6 Comments
@[manojkagitha] ,
Absolutely, the "free" nature of consuming events often creates a false sense of security. Because reusing an event doesn't impact the producer's runtime performance or core logic, teams treat them as free-for-alls.
But there is a massive difference between having the technical ability to consume an event and having the right to rely on it. Events are data assets. Without clear ownership and versioned contracts, you aren't building a decoupled system—you're just hiding tightly coupled dependencies until the next silent failure.
@[manojkagitha]
You are absolutely correct, but versioning is just one piece of the puzzle within a broader event naming standard. To safely guide publishers and consumers, we need a robust, well-defined naming taxonomy.
Looking at this from a macro perspective, the industry loves to market Event-Driven Architecture (EDA) as the ultimate tool for loose coupling. However, because multiple events must string together across an event flow to complete a single business operation, the reality is clear: EDA is technically loosely coupled, but business-wise tightly coupled.
To dive deeper into this specific paradox, I will be reposting my article, "Event-Driven Architecture: Loose Coupling, Tight Cohesion" (originally published on LinkedIn), right here shortly.
Please log in to add a comment.
The consumer-failure case from schema changes can be tested instead of governed. With consumer-driven contracts, each consumer registers the fields it actually reads, and the producer's CI fails when a change removes or retypes one of them. Combined with additive-only evolution, this catches the "required field removed" failure before deploy. The post does not cover delivery semantics, though, and that is where many Pub/Sub systems called event-driven break in practice: duplicate delivery and out-of-order events make consumers without idempotency keys corrupt state. Who should own the contract tests, the producer team or each consumer team?
@[Bubblegun]
You are absolutely correct. This post was designed to clarify the foundational boundary between raw Pub/Sub and a mature EDA, rather than deep-diving into granular execution details like schema management and delivery semantics.
To answer your question on ownership directly: The producer team must own the contract definition, but the testing execution is a shared responsibility driven by the consumer's needs.
My view is rooted in "Governance first, testing later." Just like a traditional REST API, the service endpoint defines the schema. In an asynchronous world, the producer is that service endpoint. The producer publishes fine-grained events to the broker, and while consumers selectively subscribe to fields they care about, the source of truth for the event schema must remain firmly with the producer.
Therefore, if a consumer introduces a Consumer-Driven Contract (CDC) test to enforce fields they read, that test should run inside the producer's CI/CD pipeline. The producer owns the pipeline break because they own the contract governance, but the consumer team owns the task of updating their field requirements.
Please log in to add a comment.
Please log in to comment on this post.
More Posts
- © 2026 Coder Legion
- Feedback / Bug
- Privacy
- About Us
- Contacts
- You Tube
- Tiktok
- Premium Subscription
- Terms of Service
- Early Builders
At HKJC, I have contributed to the development of integration standards, reference architectures, and training programs, resulting in multiple Solace certifications across teams. My mission is to drive enterprise innovation by advancing efficient EDA solutions and fostering collective success through technology governance and collaboration. Show less
More From Stephen
Related Jobs
- Sr. Director & Head of ArchitectureG-P · Full time · India
- Vectorworks Architecture BIM Specialistmicro1 · Temporary · Australia
- Sr. Director & Head of ArchitectureG-P · Full time · Ireland
Commenters (This Week)
Contribute meaningful comments to climb the leaderboard and earn badges!