Skip to main content

Products

SimplyQ is a cloud-based event distribution platform that allows you to send and receive events. It is a fully managed service that allows you to focus on building your application and not worry about the infrastructure.

Webhooks API​

The Webhooks API provides a way for you to send events. Manage receiving endpoints and configure routing and delivery rules.

Developers can build robust integrations that make use of our fully managed webhooks infrastructure, so you never fail to deliver a webhook. You send your events to SimplyQ and we will deliver them to your configured endpoints. With routing rules you and your customers can choose which events are delivered to which endpoints. With even more advanced configuration options you can always know you are in control, and can focus on building features your users will love, instead of worrying about the infrastructure.

Get started

Webhooks Gateway​

The Webhooks Gateway provides a way for you to receive events. Manage event sources, configure routing and delivery rules, and create integration workflows.

The Webhooks Gateway service provides a secure and reliable way to connect your web application with external systems via webhooks. With this service, you can easily receive and process webhooks from different sources, even if your application is not directly reachable from the sender.

Our Webhooks Gateway service offers end-to-end management of the webhook flow, including authentication, authorization, payload transformation (coming soon), and delivery to your application. You can also benefit from additional features such as caching, rate limiting, and error handling, ensuring that your webhook integrations are robust and reliable.

By using our fully managed Webhooks Gateway service, you can focus on building your core application functionality, without worrying about the complexities of managing webhook communication. This service allows you to streamline your integration workflows, improve your application's performance.

Use our Webhooks Gateway service to unlock the full potential of webhook integrations for your web application, and stay ahead of the competition in today's fast-paced digital world.

Get started

Event Store​

The Event Store provides a way for you to write events based on events you receive at the Webhooks Gateway. Configure Create, Upsert, Update and Delete rules for connected Webhook Gateway Pipelines. Create integration workflows that allow you to build robust integrations that make use of our fully managed event store infrastructure.

Why use SimplyQ and not building your own webhook events infrastructure​

To build the webhook events infrastructure yourself there are at least six main components that you need to build, operate and maintain:

  1. The event ingestion service

This service is responsible for receiving events from your application and storing them in a queue. This service is also responsible for validating the events and making sure they are in the correct form.

  1. Storage

Storage as with any data driven service plays a major role in how cost effective and easy to scale a system would be. The storage can be be a database, a message queue, etc.

  1. Management API

You would need to build an API that allows you and possibly your customers to manage and debug the data in the system. This API adds more reads to your storage layer and possibly other services, so you need to make sure that the API is performant and scalable.

  1. Scheduler

Often times you would want to schedule the delivery of events to your customers. This is where the scheduler comes in. The scheduler is responsible for reading the events from the queue and scheduling them for delivery. This is also where your fan-out and routing rules could be applied. THe service can also be responsible for balancing the load across multiple delivery endpoints, and ensuring all events get a chance to be delivered.

  1. Delivery service

This is the atyppical part of the system a lot of people talk about, as it needs to be optimised for outgoing requests and not incoming requests as we see in most typical services. This service is responsible for delivering the events to the configured endpoints. This service needs to be highly performant and scalable. Often times this would be a worker pool and it would provide feedback directly to the control plane to ensure the overall health of the system and your endpoints.

  1. Monitoring and alerting

This is a very important part of any system. You need to be able to monitor the health of the system and be able to alert when something goes wrong. This is also where you can monitor the health of your endpoints and alert your customers when something goes wrong.

Sign up for free