Getting Started

Event-driven architecture style on Azure

The Azure Architecture Center describes the event-driven architecture style as consisting of event producers and event consumers which can use the publish/subscribe (also called pub/sub) model.

The Particular Service Platform implements pub/sub, with each NServiceBus endpoint acting as a publisher (event producer) and/or subscriber (endpoint consumer).


  • NServiceBus publisher (event producer)

    Publishes events with business meaning in a reliable fire-and-forget style and has no knowledge of subscribers (there may be none).

  • NServiceBus subscriber (event consumer)

    Subscribed to a specific event type and reacts to it. A subscriber may also be an event publisher, since processing an event may lead to publishing more events.

  • Azure Service Bus

    The messaging service that brings together publisher and subscriber without explicitly referencing or depending on each other.


  • Events order

    Subscribers cannot rely on the order they receive published events, which may be affected by many factors such as concurrency, scaling, retries, partitioning, etc. Events and subscribers should be designed so that they do not rely on strict ordering to execute business processes.

  • Event data:

    Putting too much data on messages couples publishers and subscribers, defeating one of the main benefits of messaging in the first place. Bloated event contracts indicate sub-optimal service boundaries, perhaps drawn along technical constraints rather than business rules, or data distribution over messaging. Well designed events are lightweight contracts, focusing on sharing IDs rather than data.

Technology choices

In event-driven architectures, components are decoupled, allowing choice of the most suitable compute and data store options for a specific component or set of components.

An event-driven approach requires support for the publish-subscribe model. NServiceBus supports the publish-subscribe model for Azure Service Bus and Azure Storage Queues, independent of the underlying service capabilities.

Additional resources

Do you have questions?

Ask our solution architects

Join Udi Dahan's in-depth Advanced Distributed Systems Design course

Learn more about the course