WebSockets with Apache Ignite

[Raul Kripalani]

Hey guys,

I'd like to gauge the interest in the community for a WebSockets client for
Apache Ignite.

Such a client would allow users to build browser-based real-time enterprise
apps that interact with Apache Ignite directly, omitting the middleware for
simple use cases. Browsers would be able to run SQL queries against Ignite,
create continuous queries, cache operations, register event listeners,
subscribe to / publish on topics, etc.

It would become possible, for example, to bridge D3 visualisations that
update real-time from a continuous query via WSS without deploying any
"channeling" middleware.

Obviously this client would have to be Javascript-based.

The WebSockets endpoint on the Apache Ignite server-side would have to
support authentication and authorization (ACL), as well as SSL and
Sessions. For all this we could integrate with Apache Shiro – it gives us
integration with LDAP, JDBC and what not.

Concerning its usage potential, it would probably be restricted to agile
internal enterprise applications that require no server-side business logic
(middleware). It would make building lightweight ad-hoc apps and dashboard
incredibly easy – something useful for campaigns, events, prototyping, etc.

What do you think?

Regards,

*Raúl Kripalani*
PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data and
Messaging Engineer
http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
http://blog.raulkr.net | twitter: @raulvk

[dsetrakyan]

Raul,

I think this is a great idea. I wonder if this can be covered by Ignite
providing Node.js integration. To my knowledge, the work was started, but
somehow got put on hold. I think Irina V. got started on it at some point.

https://issues.apache.org/jira/browse/IGNITE-961

Perhaps we could pick this work back up after Ignite 1.5.

My thinking is that once we have the Node.js client, the WebSockets can be
covered by any of the numerous libraries for Node.js.

Thoughts?

D.

On Mon, Oct 26, 2015 at 12:10 PM, Raul Kripalani <[hidden email]> wrote:

> Hey guys,
>
> I'd like to gauge the interest in the community for a WebSockets client for
> Apache Ignite.
>
> Such a client would allow users to build browser-based real-time enterprise
> apps that interact with Apache Ignite directly, omitting the middleware for
> simple use cases. Browsers would be able to run SQL queries against Ignite,
> create continuous queries, cache operations, register event listeners,
> subscribe to / publish on topics, etc.
>
> It would become possible, for example, to bridge D3 visualisations that
> update real-time from a continuous query via WSS without deploying any
> "channeling" middleware.
>
> Obviously this client would have to be Javascript-based.
>
> The WebSockets endpoint on the Apache Ignite server-side would have to
> support authentication and authorization (ACL), as well as SSL and
> Sessions. For all this we could integrate with Apache Shiro – it gives us
> integration with LDAP, JDBC and what not.
>
> Concerning its usage potential, it would probably be restricted to agile
> internal enterprise applications that require no server-side business logic
> (middleware). It would make building lightweight ad-hoc apps and dashboard
> incredibly easy – something useful for campaigns, events, prototyping, etc.
>
> What do you think?
>
> Regards,
>
> *Raúl Kripalani*
> PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data and
> Messaging Engineer
> http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
> http://blog.raulkr.net | twitter: @raulvk
>