Azure Event Grid vs Beebotte

	Azure Event Grid	Beebotte
Time to "hello world" Reviewed by 3+ independent developers Ratings were given based on the average amount of time it takes to sign up to a new account and publish the first message.	4 / 5 5 = <30 min 4 = 30 min - 1 h 3 = 1-2 h 2 = 2-4 h 1 = 4+ h View code example	4 / 5 5 = <30 min 4 = 30 min - 1 h 3 = 1-2 h 2 = 2-4 h 1 = 4+ h View code example
Demos / Tutorials A selection of online demos and tutorials so you can test and see the code in action. Explore Ably's tutorials for our pub/sub messaging platform	Monitor virtual machine changes with Azure Event Grid Stream big data into a data warehouse with Event Grid & other Azure services Route custom events to web endpoint with the Azure portal & Event Grid	Quick start guide Connect Sigfox Data to Beebotte Tracking device Geolocation Beebotte View more Beebotte demos & tutorials
Documentation Reviewed by 3+ independent developers Explore Ably's documentation for our pub/sub messaging platform	4.50 / 5 Getting started guides / 5 Information architecture and developer journey / 5 API reference documentation / 5 Readability, design and navigation / 5 Quality of code / 5 Breadth and quality of tutorials / 5 “Azure Event Grid documentation is well organized in terms of information architecture, and the navigation is intuitive. The docs largely consist of quickstart guides, tutorials, samples, and Event Grid concepts. There’s also a useful comparison page with other similar Azure messaging services - Service Bus and Event Hubs. The tutorials are well written, with print screens and code samples throughout. However, they don’t cover the entire breadth of event sources and handlers that can communicate through Event Grid, which would have been incredibly helpful.“	4.50 / 5 Getting started guides / 5 Information architecture and developer journey / 5 API reference documentation / 5 Readability, design and navigation / 5 Quality of code / 5 Breadth and quality of tutorials / 5 Beebotte documentation provides a comprehensive set of tutorials and demos for different use cases. There's a quick start guide, an API playground, tutorials, demos, and libraries showing a detailed API reference for each SDK cross-linked to GitHub’s page for quick installation. The information architecture and navigation experience are quite impressive, and most things are explained clearly in the documentation. The quality of the code is pretty great. The readability, design, and navigation are mostly good as well.
Dashboard or dev console Reviewed by 3+ independent developers Sign up for free and explore Ably's pub/sub messaging platform	4.33 / 5 Ease of use / 5 Stats and reports / 5 Functionality / 5 “Azure Portal allows you to configure and monitor event pipelines built with Event Grid. Adding new events and handlers and managing them is easy enough, and the workflow is intuitive most of the time. You can also configure various logs, metrics, and alerts. All in all, the experience is good, but some tooltips would be good, so you don’t have to dig through the documentation if it’s the first time you’re using the service.“	5 / 5 Ease of use / 5 Stats and reports / 5 Functionality / 5 Beebotte provides a console (an integrated development interface with a collection of tools) that is intuitive to use. It allows you to write, read, publish, and manage data. It’s very easy to use once you get the hang of it, but you need to successfully register with Beebotte and obtain your API and secret keys in your account setting page to get started. There’s a nice section on the dashboard called Beerules that allows you to create a rule to evaluate messages published into Beebotte. There’s a monthly usage section that displays your daily and monthly (in vs. out) message stats. The console covers the core tools you need to configure, manage, and test your real-time data pipeline, allowing you to subscribe to a channel resource, and publish data. The account usage section provides stats and reports on message usages.
SDKs Note: Only official SDKs were taken into account. Explore Ably's 25+ SDKs for our pub/sub messaging platform	6 data plane SDKs Including: .NET JavaScript Go	6 SDKs Including: JavaScript Node.js Python
API structure Reviewed by 3+ independent developers	4.25 / 5 API consistency across SDKs / 5 Well structured / 5 Intuitive / 5 Simple / 5 “Event Grid APIs are split into data plane APIs and management APIs. The management APIs enable you to create, update, and delete Event Grid topics and subscriptions, while the data plane APIs enable you to post events to topics and consume events. The APIs are largely intuitive and consistent across SDKs. They’re also quite easy to use, but you need to familiarize yourself with them first, as there are tens of operations you can perform.“	5 / 5 API consistency across SDKs / 5 Well structured / 5 Intuitive / 5 Simple / 5 The Beebotte APIs are consistent and intuitive to use. The Beebotte REST APIs are available in many programming languages to help you get started, while a JavaScript client library (using WebSocket) allows you to integrate Beebotte with web application with ease. The APIs are well-structured and pretty easy to use once you take your time to go through the API reference.

Azure Event Grid

Beebotte

Getting started and developer experience

Time to "hello world"

Reviewed by 3+ independent developers

Ratings were given based on the average amount of time it takes to sign up to a new account and publish the first message.

4 / 5

5 = <30 min
4 = 30 min - 1 h
3 = 1-2 h
2 = 2-4 h
1 = 4+ h

View code example

4 / 5

5 = <30 min
4 = 30 min - 1 h
3 = 1-2 h
2 = 2-4 h
1 = 4+ h

View code example

Demos / Tutorials

A selection of online demos and tutorials so you can test and see the code in action.

Explore Ably's tutorials for our pub/sub messaging platform

Quick start guide

Connect Sigfox Data to Beebotte

Documentation

Reviewed by 3+ independent developers

Explore Ably's documentation for our pub/sub messaging platform

4.50 / 5

Getting started guides / 5

Information architecture and developer journey / 5

API reference documentation / 5

Readability, design and navigation / 5

Quality of code / 5

Breadth and quality of tutorials / 5

“Azure Event Grid documentation is well organized in terms of information architecture, and the navigation is intuitive. The docs largely consist of quickstart guides, tutorials, samples, and Event Grid concepts. There’s also a useful comparison page with other similar Azure messaging services - Service Bus and Event Hubs. The tutorials are well written, with print screens and code samples throughout. However, they don’t cover the entire breadth of event sources and handlers that can communicate through Event Grid, which would have been incredibly helpful.“

4.50 / 5

Getting started guides / 5

Information architecture and developer journey / 5

API reference documentation / 5

Readability, design and navigation / 5

Quality of code / 5

Breadth and quality of tutorials / 5

Beebotte documentation provides a comprehensive set of tutorials and demos for different use cases. There's a quick start guide, an API playground, tutorials, demos, and libraries showing a detailed API reference for each SDK cross-linked to GitHub’s page for quick installation.

The information architecture and navigation experience are quite impressive, and most things are explained clearly in the documentation. The quality of the code is pretty great. The readability, design, and navigation are mostly good as well.

Dashboard or dev console

Reviewed by 3+ independent developers

4.33 / 5

Ease of use / 5

Stats and reports / 5

Functionality / 5

“Azure Portal allows you to configure and monitor event pipelines built with Event Grid. Adding new events and handlers and managing them is easy enough, and the workflow is intuitive most of the time. You can also configure various logs, metrics, and alerts. All in all, the experience is good, but some tooltips would be good, so you don’t have to dig through the documentation if it’s the first time you’re using the service.“

5 / 5

Ease of use / 5

Stats and reports / 5

Functionality / 5

Beebotte provides a console (an integrated development interface with a collection of tools) that is intuitive to use. It allows you to write, read, publish, and manage data. It’s very easy to use once you get the hang of it, but you need to successfully register with Beebotte and obtain your API and secret keys in your account setting page to get started. There’s a nice section on the dashboard called Beerules that allows you to create a rule to evaluate messages published into Beebotte. There’s a monthly usage section that displays your daily and monthly (in vs. out) message stats.

The console covers the core tools you need to configure, manage, and test your real-time data pipeline, allowing you to subscribe to a channel resource, and publish data. The account usage section provides stats and reports on message usages.

SDKs

Note: Only official SDKs were taken into account.

Explore Ably's 25+ SDKs for our pub/sub messaging platform

6 data plane SDKs

Including:

.NET
JavaScript
Go

6 SDKs

Including:

JavaScript
Node.js
Python

API structure

Reviewed by 3+ independent developers

4.25 / 5

API consistency across SDKs / 5

Well structured / 5

Intuitive / 5

Simple / 5

“Event Grid APIs are split into data plane APIs and management APIs. The management APIs enable you to create, update, and delete Event Grid topics and subscriptions, while the data plane APIs enable you to post events to topics and consume events. The APIs are largely intuitive and consistent across SDKs. They’re also quite easy to use, but you need to familiarize yourself with them first, as there are tens of operations you can perform.“

5 / 5

API consistency across SDKs / 5

Well structured / 5

Intuitive / 5

Simple / 5

The Beebotte APIs are consistent and intuitive to use. The Beebotte REST APIs are available in many programming languages to help you get started, while a JavaScript client library (using WebSocket) allows you to integrate Beebotte with web application with ease. The APIs are well-structured and pretty easy to use once you take your time to go through the API reference.

Azure Event Grid	Beebotte
// PUBLISH TO EVENT GRID function EventGridSample() { // TODO: Enter value for topicKey let topicKey = 'enter-topic-key'; // TODO: Enter value for topic-endpoint let topicEndPoint = 'enter-topic-endpoint'; let topicCreds = new msRestAzure.TopicCredentials(topicKey); let egClient = new eventGrid(topicCreds); let topicUrl = url.parse(topicEndPoint, true); let topicHostName = topicUrl.host; let currentDate = new Date(); let events = [ { id: uuid(), subject: 'Door1', dataVersion: '2.0', eventType: 'Contoso.Items.ItemReceivedEvent', data: { itemSku : 'ContosoItemSku' }, eventTime: currentDate } ]; egClient.publishEvents(topicHostName, events).then((result) => { return Promise.resolve(console.log('Published events successfully.')); }).catch((err) => { console.log('An error ocurred ' + err); }); } EventGridSample(); // CONSUME FROM EVENT GRID module.exports = function (context, req) { const SubscriptionValidationEvent = "Microsoft.EventGrid.SubscriptionValidationEvent"; const StorageBlobCreatedEvent = "Microsoft.Storage.BlobCreated"; const CustomTopicEvent = "Contoso.Items.ItemReceivedEvent"; var parsedReq = JSON.parse(req['rawBody']); context.log('JavaScript HTTP trigger function processed a request.' + parsedReq); parsedReq.forEach(eventGridEvent => { var eventData = eventGridEvent.data; // Deserialize the event data into the appropriate type based on event type using if/elif/else if (eventGridEvent.eventType == SubscriptionValidationEvent) { context.log('Got SubscriptionValidation event data, validationCode: ' + eventData.validationCode + ', topic: ' + eventGridEvent.topic); context.res = { validationResponse: eventData.validationCode }; } else if (eventGridEvent.eventType == StorageBlobCreatedEvent) { context.log('Got Blobcreated event data, blob URI ' + eventData.url); } else if (eventGridEvent.eventType == CustomTopicEvent) { context.log('Got ContosoItemReceived event data, item SKU ' + eventData.itemSku); } }); context.done(); };	// Copyright (c) 2013-2014 Beebotte <[email protected]> // This program is published under the MIT License (http://opensource.org/licenses/MIT). ///////////////////////////////////////////////////////////// // This code uses the Beebotte API, you must have an account. // You can register here: http://beebotte.com/register ///////////////////////////////////////////////////////////// var mqtt = require('mqtt') client = mqtt.connect('mqtt://mqtt.beebotte.com', //Authenticate with your channel token, {username: 'token:YOUR_CHANNEL_TOKEN', password: ''} //alternatively, you can authenticate with your SECRET KEY //{username: 'YOUR_SECRET_KEY', password: ''} ); client.on('message', function (topic, message) { console.log(topic + ' ' + message); }); client.subscribe('mychannel/myresource'); setInterval(function() { client.publish('mychannel/myresource', 'Hello World'); }, 1000 /* 1 second */);

Azure Event Grid

Beebotte

"Hello world" code example

// PUBLISH TO EVENT GRID
function EventGridSample() {
  // TODO: Enter value for topicKey
  let topicKey = 'enter-topic-key';
  // TODO: Enter value for topic-endpoint
  let topicEndPoint = 'enter-topic-endpoint';

  let topicCreds = new msRestAzure.TopicCredentials(topicKey);
  let egClient = new eventGrid(topicCreds);
  let topicUrl = url.parse(topicEndPoint, true);
  let topicHostName = topicUrl.host;
  let currentDate = new Date();
    
  let events = [
    {
      id: uuid(),
      subject: 'Door1',
      dataVersion: '2.0',
      eventType: 'Contoso.Items.ItemReceivedEvent',
      data: {
        itemSku : 'ContosoItemSku'
      },
      eventTime: currentDate
    }
  ];
  egClient.publishEvents(topicHostName, events).then((result) => {
    return Promise.resolve(console.log('Published events successfully.'));
  }).catch((err) => {
    console.log('An error ocurred ' + err);
  });
}

EventGridSample();

// CONSUME FROM EVENT GRID
module.exports = function (context, req) {
    const SubscriptionValidationEvent = "Microsoft.EventGrid.SubscriptionValidationEvent";
    const StorageBlobCreatedEvent = "Microsoft.Storage.BlobCreated";
    const CustomTopicEvent = "Contoso.Items.ItemReceivedEvent";

    var parsedReq = JSON.parse(req['rawBody']);
    context.log('JavaScript HTTP trigger function processed a request.' + parsedReq);

    parsedReq.forEach(eventGridEvent => {
        var eventData = eventGridEvent.data; 
        // Deserialize the event data into the appropriate type based on event type using if/elif/else
        if (eventGridEvent.eventType == SubscriptionValidationEvent) {
            context.log('Got SubscriptionValidation event data, validationCode: ' + eventData.validationCode + ', topic: ' + eventGridEvent.topic); 
            context.res = {
                    validationResponse: eventData.validationCode
            };
        } else if (eventGridEvent.eventType == StorageBlobCreatedEvent) {
            context.log('Got Blobcreated event data, blob URI ' + eventData.url);
        } else if (eventGridEvent.eventType == CustomTopicEvent) {
            context.log('Got ContosoItemReceived event data, item SKU ' + eventData.itemSku);
        }
    });
    
    context.done();
};

// Copyright (c) 2013-2014 Beebotte <[email protected]>
// This program is published under the MIT License (http://opensource.org/licenses/MIT).
 
/////////////////////////////////////////////////////////////
// This code uses the Beebotte API, you must have an account.
// You can register here: http://beebotte.com/register
/////////////////////////////////////////////////////////////

var mqtt = require('mqtt')

client =  mqtt.connect('mqtt://mqtt.beebotte.com',
  //Authenticate with your channel token, 
  {username: 'token:YOUR_CHANNEL_TOKEN', password: ''} 

  //alternatively, you can authenticate with your SECRET KEY 
  //{username: 'YOUR_SECRET_KEY', password: ''} 
);

client.on('message', function (topic, message) {
  console.log(topic + '   ' + message);
});

client.subscribe('mychannel/myresource');

setInterval(function() {
  client.publish('mychannel/myresource', 'Hello World');
}, 1000 /* 1 second */);

	Azure Event Grid	Beebotte
Pub/Sub messaging Pub/Sub is a design pattern that lets any number of publishers (producers) push messages to channels (also known as topics). Multiple subscribers (consumers) can subscribe to a channel to consume published messages. Explore Ably's pub/sub messaging implementation
Message queues A message queue is a form of asynchronous service-to-service communication. Messages are stored on a queue until they are processed. Note that each message is only consumed by one subscriber (consumer). Explore Ably's message queues implementation		Limited Beebotte only stores data of a persistent message into its resources database for future read requests. Beebotte will not store data related to transient messages.
Presence Presence enables you to track the online and offline status of devices and end-users in real time and to store their state. Essential for chat apps and multiplayer games. Explore Ably's presence implementation
Message history Message history provides a means to retrieve previously published messages. For this to be possible, message data must be stored (persisted) somewhere. Explore Ably's message history implementation		Limited Message retention duration is limited to the Beebotte’s plan you choose. The maximum message retention duration for the Beebotte’s XS (free) plan is 3 months, it’s 12 months for the Small plan, while the Medium and Large plans offer unlimited message history.
Connection state recovery (stream resume) In the case of unreliable network conditions, clients may suddenly disconnect.Connection state recovery ensures that when they reconnect, the data stream resumes exactly where it left off. Explore Ably' s connection state recovery implementation
Guaranteed message ordering Ordering ensures that messages are delivered to consumers in the same order that producers publish them. Explore Ably' s guaranteed message ordering implementation
Exactly-once semantics Exactly-once is a system-wide data integrity guarantee that ensures each message is delivered to consumers exactly-once. Explore Ably' s idempotent publishing implementation
Message delta compression Message delta compression enables you to only send the changes from the previous message to subscribers each time there’s an update, instead of the entire message. Useful for use cases where there is a significant degree of similarity between successive messages. Explore Ably' s message delta compression implementation
Native push notifications Native push notifications can be used to deliver messages even when clients are offline. Useful for geolocation updates or news alerts. Explore Ably's push notifications implementation		Limited Beebotte only supports native push notifications via its BeeRule FCM Action
Webhooks Webhooks provide a mechanism to get messages and other types of events (such as clients entering or leaving channels) pushed to your servers over HTTP. Explore Ably's webhooks implementation		Limited You have to set a rule to perform this action (webhook) using Beebotte BeeRules
Serverless functions A serverless function is essentially an isolated, single-purpose piece of code that is only executed when it’ triggered by an event. For example, you can use serverless functions to send a welcome message to clients when they become present on chat channels. Note that serverless functions are usually fully managed by cloud vendors. Explore Ably's serverless functions implementation	Limited Only integrates with Azure Functions. Event Grid doesn’t have in-built support for other serverless platforms, such as AWS Lambda or Google Cloud Functions.	Limited Can only trigger serverless functions on IFTTT. Does not support other platforms, such as Google Cloud Functions, AWS Lambda, or Microsoft Azure Functions.
Built-in integrations Which popular services & systems are Azure Event Grid and Beebotte integrated with? Explore Ably's library of integrations	Webhooks Custom IFTTT Zapier Serverless functions AWS Lambda Cloudflare Workers Google Cloud Functions Microsoft Azure Functions Streaming Apache Kafka Apache Pulsar Amazon Kinesis Amazon SQS RabbitMQ AMQP	Webhooks Custom IFTTT Zapier Serverless functions AWS Lambda Cloudflare Workers Google Cloud Functions Microsoft Azure Functions Streaming Apache Kafka Apache Pulsar Amazon Kinesis Amazon SQS RabbitMQ AMQP
Known limits and constraints Find out practical limits, such as the maximum message size, or the maximum number of concurrent connections. Explore the practical limits of the Ably pub/sub messaging platform	Publisher throughput 5.000 events/sec or 1 MB/sec (whichever is met first) per topic Maximum message size 1 MB Maximum number of topics 100.000 topics per event domain Maximum number of subscribers 500 subscriptions per topic	Publisher throughput Unknown Maximum message size 16 KB for Inbound Messages Maximum number of channels Unlimited Maximum number of topics Unknown Maximum number of connections Unknown

Azure Event Grid

Beebotte

Realtime features

Pub/Sub messaging

Pub/Sub is a design pattern that lets any number of publishers (producers) push messages to channels (also known as topics). Multiple subscribers (consumers) can subscribe to a channel to consume published messages.

Explore Ably's pub/sub messaging implementation

Message queues

A message queue is a form of asynchronous service-to-service communication. Messages are stored on a queue until they are processed. Note that each message is only consumed by one subscriber (consumer).

Explore Ably's message queues implementation

Limited

Beebotte only stores data of a persistent message into its resources database for future read requests. Beebotte will not store data related to transient messages.

Presence

Presence enables you to track the online and offline status of devices and end-users in real time and to store their state. Essential for chat apps and multiplayer games.

Explore Ably's presence implementation

Message history

Message history provides a means to retrieve previously published messages. For this to be possible, message data must be stored (persisted) somewhere.

Explore Ably's message history implementation

Limited

Message retention duration is limited to the Beebotte’s plan you choose.

The maximum message retention duration for the Beebotte’s XS (free) plan is 3 months, it’s 12 months for the Small plan, while the Medium and Large plans offer unlimited message history.

Connection state recovery (stream resume)

In the case of unreliable network conditions, clients may suddenly disconnect.Connection state recovery ensures that when they reconnect, the data stream resumes exactly where it left off.

Explore Ably' s connection state recovery implementation

Guaranteed message ordering

Ordering ensures that messages are delivered to consumers in the same order that producers publish them.

Explore Ably' s guaranteed message ordering implementation

Exactly-once semantics

Exactly-once is a system-wide data integrity guarantee that ensures each message is delivered to consumers exactly-once.

Explore Ably' s idempotent publishing implementation

Message delta compression

Message delta compression enables you to only send the changes from the previous message to subscribers each time there’s an update, instead of the entire message. Useful for use cases where there is a significant degree of similarity between successive messages.

Explore Ably' s message delta compression implementation

Native push notifications

Native push notifications can be used to deliver messages even when clients are offline. Useful for geolocation updates or news alerts.

Explore Ably's push notifications implementation

Limited

Beebotte only supports native push notifications via its BeeRule FCM Action

Webhooks

Webhooks provide a mechanism to get messages and other types of events (such as clients entering or leaving channels) pushed to your servers over HTTP.

Explore Ably's webhooks implementation

Limited

You have to set a rule to perform this action (webhook) using Beebotte BeeRules

Serverless functions

A serverless function is essentially an isolated, single-purpose piece of code that is only executed when it’ triggered by an event. For example, you can use serverless functions to send a welcome message to clients when they become present on chat channels.

Note that serverless functions are usually fully managed by cloud vendors.

Explore Ably's serverless functions implementation

Limited

Only integrates with Azure Functions. Event Grid doesn’t have in-built support for other serverless platforms, such as AWS Lambda or Google Cloud Functions.

Limited

Can only trigger serverless functions on IFTTT. Does not support other platforms, such as Google Cloud Functions, AWS Lambda, or Microsoft Azure Functions.

Built-in integrations

Which popular services & systems are Azure Event Grid and Beebotte integrated with?

Explore Ably's library of integrations

Webhooks

Custom
IFTTT
Zapier

Serverless functions

AWS Lambda
Cloudflare Workers
Google Cloud Functions
Microsoft Azure Functions

Streaming

Apache Kafka
Apache Pulsar
Amazon Kinesis
Amazon SQS
RabbitMQ
AMQP

Webhooks

Custom
IFTTT
Zapier

Serverless functions

AWS Lambda
Cloudflare Workers
Google Cloud Functions
Microsoft Azure Functions

Streaming

Apache Kafka
Apache Pulsar
Amazon Kinesis
Amazon SQS
RabbitMQ
AMQP

Known limits and constraints

Find out practical limits, such as the maximum message size, or the maximum number of concurrent connections.

Explore the practical limits of the Ably pub/sub messaging platform

Publisher throughput

5.000 events/sec or 1 MB/sec (whichever is met first) per topic

Maximum message size

1 MB

Maximum number of topics

100.000 topics per event domain

Maximum number of subscribers

500 subscriptions per topic

Publisher throughput

Unknown

Maximum message size

16 KB for Inbound Messages

Maximum number of channels

Unlimited

Maximum number of topics

Unknown

Maximum number of connections

Unknown

Supported development platforms, languages, open protocols and cloud models
Development platforms & operating systems Which popular development platforms and operating systems do Azure Event Grid and Beebotte support via official SDKs? Explore the development platforms supported by Ably	Android Java / JVM iOS macOS iPadOS tvOS watchOS Mono .NET	Android Java / JVM iOS macOS iPadOS tvOS watchOS Mono .NET
Languages Which popular programming languages do Azure Event Grid and Beebotte support via offical SDKs? Explore the programming languages supported by Ably	JavaScript Node.js TypeScript Java Objective-C Swift Go PHP Python Ruby Flutter Clojure Scala	JavaScript Node.js TypeScript Java Objective-C Swift Go PHP Python Ruby Flutter Clojure Scala
Open protocols Which popular open protocols do Azure Event Grid and Beebotte support? Explore the open protocols supported by Ably	WebSocket HTTP AMQP MQTT STOMP SSE Webhooks	WebSocket HTTP AMQP MQTT STOMP SSE Webhooks
Cloud models Which popular cloud models do Azure Event Grid and Beebotte support?	Self-hosted Cloud-managed Serverless Globally-distributed	Self-hosted Cloud-managed Serverless Globally-distributed

Global and reliable edge service
Edge messaging network with latency-based routing Latency-based routing ensures that clients are always routed to the nearest datacenter and point of presence. Explore Ably's routing mechanism that mitigates network and DNS issues
Multi-region data replication (message durability) Multi-region data replication (storage) protects against single points of failure and ensures message data durability. Learn how Ably ensures message durability		Unknown
Uptime SLAs Here’s what the most common SLAs amount to in terms of downtime over a calendar year: 99.999% SLA = 5m 15s downtime per year 99.99% SLA = 52m 35s downtime per year 99.95% SLA = 4h 22m 58s downtime per year 99.9% SLA = 8h 45m 56s downtime per year 99% SLA = 3d 15h 39m 29s downtime per year Source: https://uptime.is/	99.99%	99.9% uptime
Quality of Service What QoS guarantees do Azure Event Grid and Beebotte provide natively? Explore Ably's availability and uptime guarantees for our pub/sub messaging platform	Multi-region data replication (storage) Exactly-once semantics Guaranteed message ordering Connection state recovery (stream resume)	Multi-region data replication (storage) Exactly-once semantics Guaranteed message ordering Connection state recovery (stream resume)

Security
API key authentication The simplest way to authenticate. Involves using private API keys that you can usually create and edit via a dashboard. Recommended to be used server-side, as private API keys shouldn’t be shared with untrusted parties. Explore Ably's implementation of API key authentication
Token-based authentication Which popular token-based authentication mechanisms do Azure Event Grid and Beebotte support? Note that token-based authentication is usually the recommended strategy on the client-side as it provides more fine-grained access control and limits the risk of credentials being compromised. Explore Ably's implementation of token-based authentication	Ephemeral tokens JWTs	Ephemeral tokens JWTs
Configurable rules and permissions Which types of configurable rules and permissions do Azure Event Grid and Beebotte support? Explore Ably's configurable rules and permissions	API keys rules and permissions Operation rules and permissions Admin rights	API keys rules and permissions Operation rules and permissions Admin rights
Message encryption Which types of message encryption do Azure Event Grid and Beebotte support? Explore Ably's message encryption mechanisms	Encrypted at rest Encrypted in transit Message payload encryption	Encrypted at rest Encrypted in transit Message payload encryption
Formal certifications Which formal certifications are Azure Event Grid and Beebotte compliant with? Explore Ably's security and compliance for our pub/sub messaging platform	SOC 2 TYPE I SOC 2 Type II HIPAA EU GDPR	SOC 2 TYPE I SOC 2 Type II HIPAA EU GDPR

Pricing & Support
Free package What do the free packages offered by Azure Event Grid and Beebotte consist of? Explore Ably's free package for our pub/sub messaging platform	First 100.000 operations free each month.	Not bad The free plan includes 50,000 daily messages, 5,000 persistent messages per day, unlimited channels, 3 months message history, access to all major features and basic supports, and SSL encryption.
Pricing model How are the Azure Event Grid and Beebotte pricing models calculated? Explore Ably's pricing model for our pub/sub messaging platform	Azure Event Grid uses a pay-per-use pricing model based on operations performed. Operations include ingress of events to Domains or Topics, advanced matches, delivery attempts, and management calls. The price per million operations is $0.60 (note that we have used the US as a reference point, but prices may vary across regions).	Beebotte pricing model is plan-based and calculated per month. There are three different paid plans: - $10/month for the Small plan: this covers unlimited channels, 200,000 messages per day, 15,000 persistent messages per day, 12 months history, and SSL encryption. - $30/month for the Medium plan: this covers unlimited channels, 1,000,000 messages per day, 50,000 persistent messages per day, unlimited history, and SSL encryption. - $120/month for the Large plan: this covers unlimited channels, 5,000,000 messages per day, 200,000 persistent messages per day, unlimited history, and SSL encryption. Find out more about Beebotte pricing
Enterprise package What benefits do the Azure Event Grid and Beebotte enterprise packages offer? Explore Ably's enterprise package for our pub/sub messaging platform	No Enterprise package	There is no specific Beebotte enterprise package.
Community Reviewed by 3+ independent developers Explore Ably's community support channel for our pub/sub messaging platform	2 / 5 Presence on multiple channels / 5 Size and activity / 5 “Not much seems to be going on in terms of community. There are around 350 questions on Stack Overflow about Event Grid, but they rarely exceed 30 views, and you're unlikely to find more than one answer to each. It is perhaps one of the lesser-used Azure services”.	1 / 5 Presence on multiple channels / 5 Size and activity / 5 Beebotte community is essentially non-existent. There’s a very small number of posts and only one follower on GitHub. The number of repos is very small as is the number of forks and stars. No presence on Slack, Discource, StackOverflow, or Gitter, either.
Support What types of support options and response times do Azure Event Grid and Beebotte offer? Explore Ably's support options for our pub/sub messaging platform	General support options Email, support ticket, phone, technical documentation, community support (e.g. forums or StackOverflow). Enterprise support The Professional Direct (ProDirect) plan includes 24/7 support, a Support API (to create & manage support tickets programmatically), and operational & architectural guidance from delivery managers. Response time Within 8 business hours for Developer customers Between 1 and 8 hours initial response time (depending on severity) for Standard and ProDirect customers.	General Support Options Email, technical documentation, Community support (LinkedIn or Twitter) Response time < 24 hours for general queries

Pricing & Support

Free package

What do the free packages offered by Azure Event Grid and Beebotte consist of?

Explore Ably's free package for our pub/sub messaging platform

First 100.000 operations free each month.

Not bad

The free plan includes 50,000 daily messages, 5,000 persistent messages per day, unlimited channels, 3 months message history, access to all major features and basic supports, and SSL encryption.

Pricing model

How are the Azure Event Grid and Beebotte pricing models calculated?

Explore Ably's pricing model for our pub/sub messaging platform

Azure Event Grid uses a pay-per-use pricing model based on operations performed.

Operations include ingress of events to Domains or Topics, advanced matches, delivery attempts, and management calls.

The price per million operations is $0.60 (note that we have used the US as a reference point, but prices may vary across regions).

Beebotte pricing model is plan-based and calculated per month. There are three different paid plans:

- $10/month for the Small plan: this covers unlimited channels, 200,000 messages per day, 15,000 persistent messages per day, 12 months history, and SSL encryption.

- $30/month for the Medium plan: this covers unlimited channels, 1,000,000 messages per day, 50,000 persistent messages per day, unlimited history, and SSL encryption.

- $120/month for the Large plan: this covers unlimited channels, 5,000,000 messages per day, 200,000 persistent messages per day, unlimited history, and SSL encryption.

Find out more about Beebotte pricing

Enterprise package

What benefits do the Azure Event Grid and Beebotte enterprise packages offer?

Explore Ably's enterprise package for our pub/sub messaging platform

No Enterprise package

There is no specific Beebotte enterprise package.

Community

Reviewed by 3+ independent developers

Explore Ably's community support channel for our pub/sub messaging platform

2 / 5

Presence on multiple channels / 5

Size and activity / 5

“Not much seems to be going on in terms of community. There are around 350 questions on Stack Overflow about Event Grid, but they rarely exceed 30 views, and you're unlikely to find more than one answer to each. It is perhaps one of the lesser-used Azure services”.

1 / 5

Presence on multiple channels / 5

Size and activity / 5

Beebotte community is essentially non-existent. There’s a very small number of posts and only one follower on GitHub. The number of repos is very small as is the number of forks and stars. No presence on Slack, Discource, StackOverflow, or Gitter, either.

Support

What types of support options and response times do Azure Event Grid and Beebotte offer?

Explore Ably's support options for our pub/sub messaging platform

General support options

Email, support ticket, phone, technical documentation, community support (e.g. forums or StackOverflow).

Enterprise support

The Professional Direct (ProDirect) plan includes 24/7 support, a Support API (to create & manage support tickets programmatically), and operational & architectural guidance from delivery managers.

Response time

Within 8 business hours for Developer customers

Between 1 and 8 hours initial response time (depending on severity) for Standard and ProDirect customers.

General Support Options

Email, technical documentation, Community support (LinkedIn or Twitter)

Response time

< 24 hours for general queries

Disclaimer: The information presented for Azure Event Grid was last updated on 24 March 2021 and on 28 February 2021 for Beebotte. It is possible that some details may now be out of date. If you think that’s the case, please let us know so we can update them. In any case, you should not rely solely on the information presented here and must check with each provider before deciding to integrate or buy any of these two solutions.

The Ably Platform

Products

Technology

Solutions

Industry

Why companies choose Ably

Explore

Quick links

The Ably Platform

Products

Technology

Solutions

Industry

Why companies choose Ably

Explore

Quick links

Azure Event Grid vs Beebotte

View more comparisons

Azure Event Grid vs Firebase

Azure Event Grid vs Twilio

Beebotte vs Firebase

Beebotte vs Twilio

More to explore

About Ably

Documentation

Compare our tech

Try our APIs for free

Talk to our technical team