|Provider of the connector:||
|Type of license:||
Pub/Sub in itself means publish/subscribe messaging pattern. It is a form of asynchronous service-to-service communication one uses in a serverless and microservices (such as elastic.io’s) architecture. Essentially, it allows users to receive any message published to a specific topic they have previously subscribed to.
The advantage of the Pub/Sub model as opposed to, say, other design patterns such as message queuing and event brokers, is that it is more flexible and scalable. For one, messages can move between different components of the system without those components being aware of each other’s identity. Some very well-known messaging frameworks – for example, Apache Kafka and RabbitMQ – are based on the Pub/Sub pattern.
About Pub/Sub integration connector
This is elastic.io’s own private connector to work with all other connectors in your integration workflows. It was developed specifically for the elastic.io platform, and it comes with the platform by default.
The Pub/Sub integration connector, as the name suggests, supports both triggers and actions. This means that you can use it either to execute (subscribe) or to act upon (publish) a certain event. It can be used in multiple different scenarios. For example, you can subscribe to a downstream service in order to get notifications about each new user signup on a specific service.
To complement the Pub/Sub integration connector, we have the so called Topics as part of our integration platform. Follow the Documentation link above to find more about that and what you need to do to set everything up.
Due to the fact that it is under the proprietary license, you cannot change or extend this connector yourself. If you have any questions, you’re welcome to contact our pre-sales team at ps[at]elastic.io.
PLEASE NOTE: You need to have an account on the elastic.io integration platform in order to use the Pub/Sub integration connector. You can sign up for a free 14-day trial here.