Kaazing AMQP Edition


The Kaazing WebSocket Gateway - AMQP Edition provides highly scalable, near zero-latency, full-duplex communication over the Web between an AMQP-compatible messaging system and a browser or mobile client.

Developers can use the same AMQP APIs they already know, enabling rapid development and deployment of Rich Internet Applications that can be indistinguishable from desktop applications.

  • Live Web
  • Simplified & Unified Architecture
  • Massively Scalable & Performance Optimized
  • Unsurpassed
  • Rapid Development & Ease of Integration
  • Mobile Cross-platform Support

Live Web

All client APIs are built on top of the WebSocket APIs, all communications are based on the WebSocket standard when WebSocket is available.

All data communications are based on WebSocket or Kaazing's WebSocket emulation in order to provide full duplex connectivity at all times. The server can push data to the client and the client can push data to the server.

Events drive all interactions, whether coming from the server or from the client.

Kaazing supports any protocol that would normally run over TCP, and makes it available over WebSocket. Some messaging protocols such as JMS, XMPP and AMQP support both synchronous and asynchronous message patterns.

Browser clients and mobile devices can publish and subscribe to exchanges that broadcast messages to many consumers.

Browser clients and mobile devices can send and receive from exchanges with bound queues.

Messages in guaranteed message deliver are persisted on the broker until all subscribed and online clients have consumed them: if clients are offline, messages are not persisted unless the client subscribed with a durable subscription.

The message payload can be either binary or text. It is not required to text-encode binary payloads.


Simplified & Unified Architecture

Kaazing supports clustering and load balancing without the need for extra load balancers. Simply configure the Gateway to provide clustering and load balancing.

When a server in a cluster of Gateways fails, connections are automatically offloaded to other Gateways.

Failed gateway connections are automatically offloaded to available Gateways within the cluster.

The Gateway can be configured to use TLS/SSL for client and server connections

By leveraging a WebSocket-based architecture using Kaazing, much less CPU power is required to service the same number of clients with real time messaging.

Clients do not need to download any additional software or plugins to run Kaazing based code in the browser.

Ready to use Ubuntu instances complete with fully functional Kaazing Gateway are available on the Amazon Marketplace.


Massively Scalable & Performance Optimized

Maximize bandwidth usage and minimize latency and CPU usage; with Kaazing, you can reach many more users with less CPU power.

Hundreds of thousands of concurrent clients can be scaled horizontally putting minimal pressure on your messaging system.

Offering volume-tiered data delivery services or to cap bandwidth utilization

Kaazing leverages state of the art messaging protocols to reduce bandwidth and network latency.

Control the traffic to your clients by selectively restricting the bandwidth available to any specific client.

Significantly lowered latency for better response time and decreased bandwidth to minimize data usage.

Get It!

Whitepaper story download here.

> download


Unsurpassed Security

Kaazing Gateway integrates with Java Authentication and Authorization Service (JAAS), thus supporting pluggable authentication and authorization modules. Write login handlers (server-side) and challenge handlers (client-side) to handle tokens from popular security vendors or public token providers such as Facebook or Twitter, or your own proprietary token service.

Kaazing’s SSO framework readily integrates with any existing security framework via JAAS.

Kaazing WebSocket Gateway supports SPNEGO-based Kerberos security, which you can integrate with your existing infrastructure to provide Single Sign-On capability. Kaazing is first in the world to offer SPNEGO-based Kerberos authentication using WebSocket over the Web.

Share the data from your back-end systems and applications over the Web without exposing them to everyone on the Internet. Kaazing WebSocket Gateway is ideal to place in the DMZ to act as a front-line access point for those back-end systems that can reside safely in the trusted network.

Any token can be re-validated periodically without logging out the user.

Fine-grained access control to specify which domains can access your services and applications. For example, you can have public services or a whitelist to only allow specific origin domains.

All Kaazing Gateways are Veracode certified with an AAA rating

Supports WebSocket Secure (WebSocket + TLS/SSL) standard WSS encryption

TLS/SSL is used to validate the Gateway's identity to the client and encrypt data. However you can also use TLS/SSL to validate a client's identity by requiring the client to present a certificate when it is attempting to connect to the Gateway.

Credentials can be obtained via single sign on and injected directly into the protocol to match credentials on the broker. Available out of the box in AMQP but can also be added to any custom protocol implementation.

The Gateway has the capacity to be distributed across DMZs so that each DMZ layer offers protection for the layer behind it. Users that don’t authenticate can fail fast closer to the user/client rather putting a burden on the center only to discover a user is not valid.

Kaazing WebSocket Gateway unifies your architecture by acting as a single access point with the exact same APIs for your back-end services for all supported client types across native WebSocket or emulation.


Rapid Development & Ease of Integration

All protocol libraries supported by Kaazing are available in JavaScript. Any modern browser with native support for WebSocket can connect to the Gateway. But that's not all. Many environments can't or won't upgrade their browsers and Kaazing WebSocket Gateway makes sure they aren't left behind. Kaazing's client emulation technology ensures older browsers can enjoy the benefits of Kaazing WebSocket Gateway with almost the same performance as native without any API changes. Emulation ensures your JavaScript application will run even on IE6.

All protocol libraries supported by Kaazing are available on Flash/FLEX

All protocol libraries supported by Kaazing are available on ,NET/Silverlight

Integrate with Microsoft Excel by creating an RTD Server using the .NET client library. You can dynamically send data in and out of Excel, live, and in real-time. See the Excel Stock Ticker Demo.

All Kaazing Gateways support the standard WebSocket client API. But that’s not all, even when WebSocket is not available, all WebSocket based code will continue to work using the emulation layer. All that is required is to declare the Kaazing JS WS library.

Get full AMQP 0-9-1 end-to-end communication, directly from the client to the message broker. Developers use a simple to use API to leverage the AMQP protocols in order to perform simple operations such as publish and subscribe in JavaScript in the browser, Flash / Flex / Air clients, Java Clients, and native iOS. This allows you to connect standard Web applications to AMQP message brokers transparently over WebSocket.

Kaazing allows you to extend any custom protocol out to the web while still leveraging many of the cutting edge Enterprise features.

Kaazing allows you to create libraries for any custom protocol while still leveraging many of the cutting edge Enterprise features.

Manage and monitor Kaazing WebSocket Gateway connections and activity via JMX.

Monitor Kaazing WebSocket Gateway via a rich HTML5 web client connected via WebSocket

Kaazing's WebSocket AccelerationTM offers enterprise WebSocket emulation when native WebSocket is not available. This includes support for older web & mobile browsers such as Android, Safari, Opera, and MS IE6+. In addition, the technology provides emulation for Cross-Origin Resource Sharing (CORS) with WebSocket, Cross-document Messaging, and Server-Sent Events (SSE).


Mobile Cross-platform Support

Using WebSocket and a messaging protocol significantly reduces the battery consumption on mobile devices as compared to http.

Each message you send over a WebSocket has only two extra bytes to frame the beginning and end of the message. On the other hand, current HTTP communication such as Ajax or Comet include a large number of HTTP headers which are typically 1000 or more bytes. Therefore using HTML5 WebSocket can result in a drastic reduction in bandwidth, even on the order of 500x lower.

Kaazing Product Editions

Learn about
our product

> learn more

Case Studies

> download
Kaazing Datasheets Whitepapers and Case Studies
Watch Kaazing Product Demos

View Demos

> watch

Free version of Kaazing Gateway softwareGet our
full, free
of Kaazing

> download