Blog

Deploy IOT and Real-time web use cases with AWS MSK and tenefit.cloud without the need for Kafka Connect, intermediary brokers, or proprietary "Push" services.

tenefit.cloud is an iPaaS that allows you to build highly resilient and scalable real-time mobile and web apps powered by Apache Kafka. It works by seamlessly extending Kafka data streams over the web using Server Sent Events (SSE).

Developing a Kafka-powered, real-time web app has never been this easy. You no longer need your own Kafka server to try out tenefit.cloud as we now offer one for you. Simply use your Kafka client library of choice to publish data to our Sandbox (located at kafka-sandbox.tenefit.cloud:9092). For each “topic” that you create within the Sandbox, tenefit.cloud will automatically generate a Server-sent Event (SSE) endpoint that will receive a stream of its underlying topic’s data. Drop this endpoint into a desktop or mobile application and you’re ready to delivery real-time features and functionalities!

Happy New Year! As a company, our resolution this year is a bold one – provide solutions to customers that carry ten times the benefit in terms of performance, security and usability. To reflect this ambition, we are excited to announce our new company name – Tenefit!

There are some solutions out there that turn your smartphone into a Wii-style controller, but many of them require a dedicated app on your phone and even a browser plugin on your desktop. With HTML5 and WebSockets you can achieve this very quickly and easily without the need of pre-installing anything on your machine or your phone.

What makes WebSockets especially compelling is that they allow you to extend the reach of enterprise protocols, like JMS, XMPP and AMQP, all the way to the browser. In this demonstration I show an example of implementing the VNC protocol, RFB, over WebSockets.

How can you tell if your WebSocket connection is native or emulated? This question came up during our recent webcast.

There’s a great discussion going on over at InfoQ about the role and future of REST in light of WebSockets. Mark Little’s article collects a handful of quotes and opinions around the topic, giving a well rounded view. With a few exceptions there is a consensus that while WebSockets may not completely take over Web Services and REST, there is a paradigm shift going into that direction. Here are a few of the interesting opinions: Nathan Evans: The true bi-directional capability offered by WebSockets is a first for any HTTP-borne protocol. It is something that neither SOAP nor REST have. And which Comet/push/long-polling can only emulate, inefficiently. The bi-directional capability is inherently so good that you could tunnel a real-time TCP protocol such as Remote Desktop or VNC over a WebSocket, if you wanted.

This is a two-part blog post that discusses HTML5 WebSocket and security. In this, the first post, I will talk about the security benefits that come from being HTTP-compatible and the WebSocket standard itself.