More comparisons

Azure Service Bus vs Lightstreamer

This Azure Service Bus vs Lightstreamer comparison was created based on reviews from developers and our best attempts to perform analysis by looking at documentation and other publicly available resources.

Need help choosing a realtime messaging solution?

Contact us

Azure Service Bus

Lightstreamer

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
2 / 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

Documentation

Reviewed by 3+ independent developers

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

Getting started guides4 / 5

Information architecture and developer journey4 / 5

API reference documentation5 / 5

Readability, design and navigation5 / 5

Quality of code3 / 5

Breadth and quality of tutorials5 / 5

“The resources for getting started with Azure Service Bus are thought out and clear. Documentation is pretty detailed, with sufficient examples and tutorials. The API docs are well organized around concepts and different programming languages. As a minus, some code samples are not updated with the latest constructs and data structures.“

2.50 / 5

Getting started guides2 / 5

Information architecture and developer journey1 / 5

API reference documentation4 / 5

Readability, design and navigation1 / 5

Quality of code3 / 5

Breadth and quality of tutorials4 / 5

“Lightstreamer documentation is overall disappointing. First of all, it’s all over the place in terms of format: from GitHub READMEs to the most basic of HTML pages to PDFs. There’s even a slide deck. Resources are seldom cross-linked, which makes the docs hard to follow. The entire design of the website is from the last century. It’s aesthetically hideous, and the navigation experience is underwhelming. The only positive things are the API reference, which is quite comprehensive, and the GitHub tutorials, which are explained well.“

Dashboard or dev console

Reviewed by 3+ independent developers

Sign up for free and explore Ably's pub/sub messaging platform
4.67 / 5

Ease of use4 / 5

Stats and reports5 / 5

Functionality5 / 5

“The interface is really informative and filled with various types of details, stats, and graphs. For example, selecting a specific topic will show active, scheduled, and dead-letter message count. For new starters, though, it can be a little overwhelming to get the hang of it and understand all the concepts and features involved.”

4 / 5

Ease of use5 / 5

Stats and reports5 / 5

Functionality2 / 5

“Lightstreamer provides a monitoring dashboard that shows various realtime metrics and stats related to the server-side, such as connections, sessions, or throughput. The event log is pretty useful, showing successful operations/events, warnings, and errors. It’s intuitive and straightforward to use, although the UI is dull and ugly. Unfortunately, there’s no dev console or portal with more extensive functionality to allow you to create and manage resources.“

SDKs

Note: Only official SDKs were taken into account.

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

7 SDKs

Including:

  • .NET

  • PHP

  • Node.js

10 production-ready client SDKs

Including:

  • Android

  • iOS

  • Node.js

API structure

Reviewed by 3+ independent developers

4 / 5

API consistency across SDKs4 / 5

Well structured5 / 5

Intuitive4 / 5

Simple3 / 5

“The APIs are fairly well-structured and named intuitively, with 3 categories described in detail. And while they are intuitive, it takes a bit to get familiar with the APIs as they’re not necessarily the most simple ones. You need to spend some time digging through the docs and GitHub READMEs, especially since there are some inconsistencies across SDKs.”

3.25 / 5

API consistency across SDKs4 / 5

Well structured4 / 5

Intuitive3 / 5

Simple2 / 5

“Lightstreamer provides APIs covering many languages, operating systems, and development platforms, such as Java, .NET, JavaScript, or iOS. There’s a separate API reference page for each SDK - a highlight in otherwise mediocre documentation. The references are pretty detailed, and the APIs are fairly well structured and consistent across SDKs. But they aren’t simple, and it takes some time to wrap your head around them. They perhaps don’t have the most intuitive naming conventions, and the code samples included are not as clear as they could be“.

Azure Service Bus

Lightstreamer

"Hello world" code example
// Send message
const { ServiceBusClient } = require("@azure/service-bus"); 

// Define connection string and related Service Bus entity names here
const connectionString = "";
const topicName = ""; 

async function main(){
  const sbClient = ServiceBusClient.createFromConnectionString(connectionString); 
  const topicClient = sbClient.createTopicClient(topicName);
  const sender = topicClient.createSender();

    try {
        for (let i = 0; i < 10; i++) {
          const message= {
            body: `Hello world! ${i}`,
            label: `test`,
            userProperties: {
                myCustomPropertyName: `my custom property value ${i}`
            }
          };
          console.log(`Sending message: ${message.body}`);
          await sender.send(message);
        }

        await topicClient.close();
      } finally {
        await sbClient.close();
      }
}

main().catch((err) => {
  console.log("Error occurred: ", err);
});

// Subscribe to messages
const { ServiceBusClient, ReceiveMode } = require("@azure/service-bus"); 

// Define connection string and related Service Bus entity names here
const connectionString = "";
const topicName = ""; 
const subscriptionName = ""; 

async function main(){
  const sbClient = ServiceBusClient.createFromConnectionString(connectionString); 
  const subscriptionClient = sbClient.createSubscriptionClient(topicName, subscriptionName);
  const receiver = subscriptionClient.createReceiver(ReceiveMode.receiveAndDelete);

  try {
    const messages = await receiver.receiveMessages(10);
    console.log("Received messages:");
    console.log(messages.map(message => message.body));

    await subscriptionClient.close();
  } finally {
    await sbClient.close();
  }
}

main().catch((err) => {
  console.log("Error occurred: ", err);
});
// Lightstreamer server 

// Data adapter xml file

<?xml version="1.0"?>
<adapters_conf id="HELLOWORLD">
    <metadata_provider>
        <adapter_class>com.lightstreamer.adapters.metadata.LiteralBasedProvider</adapter_class>
    </metadata_provider>
    <data_provider>
        <adapter_class>HelloWorldDataAdapter</adapter_class>
    </data_provider>
</adapters_conf>

// Package.json file for server requirements configuration

{
  "requires": true,
  "lockfileVersion": 1,
  "dependencies": {
    "lightstreamer-client-web": {
      "version": "8.0.2",
      "resolved": "https://registry.npmjs.org/lightstreamer-client-web/-/lightstreamer-client-web-8.0.2.tgz",
      "integrity": "sha512-UFEtoW+K2H+9PZNqdVGD6TqCBZNbsjC3TuZn5M1ee6D/aXlR8yzruKBXfQNdD0pgcpgpcKoMd/dyfeZxOf6EIg=="
    }
  }
}

// Lightstreamer client 

// HTML file with importing lightstreamer.min.js and require.js

<html>
  <head>
    <title>Hello World with Lightstreamer</title>
    <script src="https://cdnjs.cloudflare.com/ajax/libs/require.js/2.3.6/require.js"></script>
    <script src="lightstreamer.min.js" data-lightstreamer-ns="Ls"></script>
  </head>

  <body>
    <div data-source="lightstreamer" data-grid="hellogrid" data-item="greetings" data-field="message">loading...</div>
    <div data-source="lightstreamer" data-grid="hellogrid" data-item="greetings" data-field="timestamp">loading...</div>

Azure Service Bus

Lightstreamer

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

Queues are supported only via the Lightstreamer JMS Extender, which connects to any third-party JMS server and makes JMS (Java Message Service) available on the Web. Any HTML page running inside a web browser and any Node.js application instantly become JMS clients, able to publish and subscribe on JMS topics and queues.

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

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

Limited

By default, Azure Service Bus cannot guarantee that messages are delivered in the order you want them to be processed by a subscriber at all times. You can theoretically force message ordering, but it comes at the expense of other features.

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

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

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

Can only trigger Azure Functions. Azure Service Bus doesn’t have in-built support for other serverless platforms, such as AWS Lambda or Google Cloud Functions.

Built-in integrations

Which popular services & systems are Azure Service Bus and Lightstreamer 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

Throughput

Unknown

Maximum message size

256 KB for Standard tier, 1 MB for Premium tier.

Maximum number of topics

10.000 for the Basic or Standard tier. The total number of topics and queues in a namespace must be less than or equal to 10.000.

For the Premium tier, 1.000 per messaging unit (MU). Maximum limit is 4.000.

Maximum number of concurrent connections

NetMessaging: 1.000 per namespace

AMQP: 5.000 per namespace

Throughput 

Depends on server capacity (Enterprise and Enterprise Ultimate packages). 

1 message/second for each subscription done by each client (community/free package).

Maximum message size 

Unknown

Maximum number of channels

Unknown

Maximum number of concurrent connections

Depends on server capacity

Supported development platforms, languages, open protocols and cloud models

Development platforms & operating systems

Which popular development platforms and operating systems do Azure Service Bus and Lightstreamer support via official SDKs?

Explore the development platforms supported by Ably
  • Androi𝗱
  • Java/JVM
  • iOS
  • macOS
  • iPadOS
  • tvOS
  • watchOS
  • Mono
  • .NET
  • Androi𝗱
  • Java/JVM
  • iOS
  • macOS
  • iPadOS
  • tvOS
  • watchOS
  • Mono
  • .NET

Languages

Which popular programming languages do Azure Service Bus and Lightstreamer 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 Service Bus and Lightstreamer support?

Explore the open protocols supported by Ably
  • WebSocket
  • HTTP / REST
  • AMQP
  • MQTT
  • STOMP
  • SSE
  • Webhooks
  • WebSocket
  • HTTP / REST
  • AMQP
  • MQTT
  • STOMP
  • SSE
  • Webhooks

Cloud models

Which popular cloud models do Azure Service Bus and Lightstreamer 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

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.9%

Unknown

Quality of Service

What QoS guarantees do Azure Service Bus and Lightstreamer 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

Limited

Lightstreamer authentication involves the usage of user & password credentials.

Token-based authentication

Which popular token-based authentication mechanisms do Azure Service Bus and Lightstreamer 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 Service Bus and Lightstreamer 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 Service Bus and Lightstreamer 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 Service Bus and Lightstreamer compliant with?

Explore Ably's security and compliance for our pub/sub messaging platform
  • SOC 2 TYPE I
  • SOC 2 Type II
  • HIPAA
  • ISO 27001
  • EU GDPR
  • SOC 2 TYPE I
  • SOC 2 Type II
  • HIPAA
  • ISO 27001
  • EU GDPR
Pricing & Support

Free package

What do the free packages offered by Azure Service Bus and Lightstreamer consist of?

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

No free package

Lightstreamer’s free package (the community edition) provides a license for one server and unlimited clients. However, the message rate is throttled at one message per second, and some features are unavailable (such as clustering or TLS support).

Pricing model

How are the Azure Service Bus and Lightstreamer pricing models calculated?

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

Azure Service Bus comes in Basic, Standard, and Premium tiers.

Basic tier pricing is calculated based on the number of messaging operations (any API call to Azure Service Bus) and costs $0.05 per million operations

Standard tier pricing is calculated based on:

- number of messaging operations (first 13 million ops/month free, a base charge of $0.0135/hour and variable price depending on the number of ops - between $0.20 and $0.80 per million ops).

- number of brokered connections (AMQP connections or HTTP calls to Service Bus) - depending on the number of connections, the price can be between $0.03 and $0.025 per connection/month

- number of hybrid connections & WCF relays. For hybrid connections, the monthly price is $9.782 per listener + a data transfer overcharge of $1/GB. As for relays, pricing is based on usage ($0.10 for every 100 relay hours) and messages ($0.01 for every 10.000 messages)

Premium pricing is calculated based on hourly usage at $0.928 per hour.

Please note that we have used the US as a reference point, but prices may vary by region and there are further differences based on the type of support package.

Lightstreamer has a complex and confusing pricing model. First, you must choose between the community edition (free) and the enterprise edition (paid). When you select enterprise, you must then opt between the Enterprise or the Enterprise Ultimate package (the latter includes all client APIs, superior message rates, and all features). On top of this, you must choose a licensing scheme, of which there are six options in total. Some examples: Perpetual Upfront per Server License, Monthly Pay-as-you-go Per Core-Hour License, Annual Upfront per Client Licence.

Once you choose a licensing scheme, you must also choose a license type, such as Demo, Evaluation, Production, or Hot-Standby.

There’s no transparency regarding cost estimation or concrete numbers (at least not on their website).

Enterprise package

What benefits do the Azure Service Bus and Lightstreamer enterprise packages offer?

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

The Premium tier is the equivalent of an enterprise package.

Key benefits 

  • 1 MB message size

  • Resource isolation

  • Geo-disaster recovery

  • Availability zones support

Lightstreamer has an Enterprise Ultimate package that includes all client APIs (different programming languages), provides unlimited messages without throttling, and grants access to all features.

Community

Reviewed by 3+ independent developers

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

Presence on multiple channels4 / 5

Size and activity2 / 5

“The Azure community is quite large and present on multiple channels, such as Stack Overflow, Microsoft Developer Network (MSDN) forums, or Microsoft Q&A. However, when it comes specifically to Service Bus, the active community is significantly smaller - there aren’t as many topics or conversations related to Service Bus as one would expect, and sometimes questions go unanswered.”

2 / 5

Presence on multiple channels2 / 5

Size and activity2 / 5

“The Lightstreamer community is small. There is some activity going on on the Lightstreamer forums - usually people raising issues and asking for clarifications that arguably should have been clear from the documentation. Beyond forums, the Lightstreamer community is basically non-existent. There are only about 30 threads in total on Stack Overflow, and, although there are over 140 Lightstreamer repos on GitHub, they barely have a few stars or open issues and almost no pull requests.“

Support

What types of support options and response times do Azure Service Bus and Lightstreamer 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, support forums, phone, technical documentation.

Enterprise support

Lightstreamer provides 8x5 and 24x7 technical support for enterprise and enterprise ultimate packages.

Response time

Unknown

Disclaimer: The information presented for Azure Service Bus was last updated on 30 September 2020 and on 7 December 2020 for Lightstreamer. 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.