Stream data to browsers, mobile apps and IoT devices quickly, securely and at unprecedented scale. kaazing.io works with what you have, allowing you to launch realtime digital products and features at record pace. Whether your backend is a REST API or Kafka messaging system, kaazing.io will stream data out of it to your client of choice relying solely on web standards (no client libraries needed).
//HTML5 Server-Sent Events used for outbound kaazing.io streaming
var stream = new EventSource(
'https://streams.example.com
);
var handler = function(event) {
console.log(event.data);
};
stream.addEventListener('message', handler, false);
Focus on awesome features and not on deploying, managing and scaling server infrastructure. kaazing.io runs as a global infrastructure network capable of hyper-low latent data streaming to anywhere in the world.
kaazing.io is not just cloud-hosted software – its a true cloud-native solution. Based on the Reaktivity Project, it’s optimized for cloud hardware, resulting in unrivaled performance at unprecedented cost.
Kafka powers event-driven, server-side capabilities, but it can also act as a highly effective backend for realtime frontend apps.
Kafka powers event-driven, server-side capabilities, but it can also act as a highly effective backend for realtime frontend apps. kaazing.io can seamlessly push data out of a Kafka instance (no matter where or how it is running) to mobile and desktop devices using HTML standards such as SSE.
REST APIs are often polled for the latest information; however, when updates are unpredictable or need to be continuously delivered to multiple clients, polling becomes highly inefficient.
REST APIs are often polled for the latest information; however, when updates are unpredictable or need to be continuously delivered to multiple clients, polling becomes highly inefficient. kaazing.io can monitor an API for changes and proactively push updates to consumers the moment they are available.
Large IoT systems have endpoints speaking different protocols such as MQTT and AMQP. When data from these endpoints has to be delivered to a service such as Kafka, a cluge of brokers must be managed.
Large IoT systems have endpoints speaking different protocols such as MQTT and AMQP. When data from these endpoints has to be delivered to a service such as Kafka, a cluge of brokers must be managed. kaazing.io’s protocol conversion capabilities eliminates the need of individual brokers streamlining an overall IoT architecture.
To provide a streaming solution that would be unrivaled in terms of performance and extensibility, Kaazing contributed to a now approach to networking through the Reaktivity Project. Reaktivity decouples the Protocol Stack allowing each layer to be executed in parallel on separate CPU cores. Layers communicate over shared memory resulting in a modular framework that maximizes throughput with predictable low latency.
Kaazing recognizes that cloud solutions can present security concerns for enterprises that run backend and middleware services behind firewalls. To address this, kaazing.io will come with a connector that will allow it to securely reach such services without exposing firewall ports. In addition, expected authentication and encryption capabilities come standard.
