Events Hub Quick Guide

Throughout the documentation, you will see some terms specific to the messaging context. To make understanding easier, we explain them:

Events Hub allows you to manage an event distribution architecture from a low-code interface, which doesn’t require advanced programming knowledge. Within it, you can register and manage event publishers and subscribers completely independently.

For Events Hub to know which subscribers should receive which events, there are publication and subscription routes, forming a channel for event reception and distribution. These routes are defined through topics, handlers and contexts, each with a specific path that is added to the publication URL. When publishers submit requests to Events Hub, we guarantee that they are distributed only to registered subscribers for that event.

In addition to managing event publication and subscription, Events Hub ensures delivery to subscribers through:

To ensure security throughout the events management process, you can add interceptors in the receiving flow. This allows you to control the access of publishers, which can be validated by an external server.

For subscribers, we include a digital signature along with all distributed events to validate the origin of requests. In addition, you can configure a static or dynamic security token for secure information traffic.

Topics, handlers and contexts are the elements that form the event publishing and subscription channel. They organize the routes for receiving and distributing events, ensuring that messages reach the correct subscribers.

The topic is the last placeholder of the publication URL and it’s through it that the Events Hub finds the subscribers that should receive each event. Publishers send requests using the publication URL of the topic, and Events Hub forwards the events to all of the topic’s active subscribers.

Handlers are topic aggregators, used to group topics logically. They are also responsible for applying security policies and event delivery, which will be shared with all topics within it.

Contexts allows you to reuse topics in different scenarios. The external authorization server is defined by context, which means that when two different contexts are made available for a topic, it’s possible to use two different authorization endpoints for the same topic.

Handlers are created and managed on the Handlers screen. In the handler’s registration and editing screen, you can:

Events Hub allows the two sides of event integration, producers and consumers, to be registered in an intuitive and independent way.

Publishers are the source of events. They are registered on the Publishers screen. You can create them or import an app from the Sensedia API Platform.

During registration, you connect the publisher to the topics to which it will send events. Additionally, you choose which contexts will be shared with it.

Subscribers are who receive the events. They are registered on the Subscribers screen. When registering a subscriber, you subscribe them to the topics they will receive events from and also choose which contexts will be shared with them.

On the Policies screen, you can define the security measures for publishers and event delivery to subscribers. This includes:

Security for publishers is ensured by interceptors that validate their identity, such as OAuth, JWT, Client ID and Access Token. In addition, you can filter publishers' access by IP.

The policies registered on the Policies screen are applied to handlers in the process of creating/editing handlers. This means that all topics grouped under a handler use the same policy. The external publisher authorization server is defined at the context level on the Authorizations screen.

Events Hub implements layers of security that allow subscribers to verify the origin of messages received.

First, we pass a digital signature in all requests to subscribers. This signature is a JWT token generated from a mutual-knowledge key (known by the subscriber and Events Hub), sent when registering subscribers.

As another security requirement for subscribers, it’s possible to configure a static or dynamic token that must also be passed in requests.

The Event Status screen displays the list of events received from publishers.

You can follow the events received in detail via the Event Status screen. For each event, the attempts and distribution history to subscribers are shown.