Company›Newsroom›Hazelcast Announces Unlimited Application Access to Leading Open Source Operational In-memory Computing Platform

By Hazelcast Comms

Oct 28, 2015

Back to Newsroom

Hazelcast Announces Unlimited Application Access to Leading Open Source Operational In-memory Computing Platform

Client Protocols Publicly Published and Native Clients for C++ and .NET All Made Open Source

News highlights:

  • Hazelcast® publishes Open Binary Client Protocol for Hazelcast 3.5 & 3.6, supporting community development of custom APIs for any programming environment.
  • Native Hazelcast clients for C++ and .NET made open source allowing community members to use them as building blocks for new clients and to act as further examples of native API development.
  • New unlimited client access offerings opens open in-memory computing door for NodeJS, Python, Ruby, Go programmers as well as bringing Hazelcast’s enterprise grade open source technology to the Azure and .NET markets.

Palo Alto, Calif., 28 October 2015 – Hazelcast today announced it had made its Open Binary Client Protocol, for Hazelcast versions 3.5 and 3.6, publically available in a move to further support community development of custom APIs. In addition, Hazelcast’s native clients for C++ and .NET will become open source to encourage developers to use them as building blocks for new client API development. Critically, Hazelcast is now a step closer to becoming platform-independent as developers are now able to write clients in the program language of their choice.

The publishing of the client protocols enables developers to build only as much APIs as they need; providing them with another route to devops optimization. The Open Binary Client Protocol is based on writing bytes and receiving bytes from a TCP connection, therefore any programming language that has the capability to write and receive bytes over a TCP socket now has the option to become a Hazelcast client, regardless of platform.

For web application development, Hazelcast is now more accessible and can be integrated into any backend by writing a client in a native backend language. The Open Binary Client Protocol is published in two documents: Specification – Developer Preview and Client Implementation Guide – Developer Preview.

Additionally, Hazelcast is making native C++ and .NET clients open source. The decision to change C++ and .NET clients to open source is in line with Hazelcast’s strategy of supporting community contributors who require an in-memory computing capability and are looking to develop clients for different languages, such as NodeJS, Python, Ruby and Go.

Greg Luck, CEO of Hazelcast, said: “The developer community has been vocal in expressing its desire to use Hazelcast more widely in different environments. The decisions we have taken are intended to make it as easy as possible for developers to use in-memory computing techniques in any programming environment.”