This short video explains why companies use Hazelcast for business-critical applications based on ultra-fast in-memory and/or stream processing technologies.
Stream processing is a hot topic right now, especially for any organization looking to provide insights faster. But what does it mean for users of Java applications, microservices, and in-memory computing?
In this webinar, we will cover the evolution of stream processing and in-memory related to big data technologies and why it is the logical next step for in-memory processing projects.
Now, deploying Hazelcast-powered applications in a cloud-native way becomes even easier with the introduction of Hazelcast Cloud Enterprise, a fully-managed service built on the Enterprise edition of Hazelcast IMDG. Can't attend the live times? You should still register! We'll be sending out the recording after the webinar to all registrants.
Andrey's been involved in design and development of various web apps and systems for many years and always enjoyed it. Came a long road from a greenhorn junior developer in a small product team to a solution architect in a large company. Some time ago joined Hazelcast engineering team and started working on the company's products, including Node.js client library. Apart from that, Andrey is a part of the Node.js core collaborators team, constantly learns new stuff from others and shares his experience with the community.
No posts were found matching that criteria.
As you may already know, the Hazelcast In-Memory Data Grid (IMDG) ecosystem includes a variety of clients for different languages and runtimes, which includes Node.js client library as a part of that list. You can use Hazelcast clients in various cases, including, but not limited to the following: Building a multi-layer cache for your applications […]
Hazelcast Node.js client 4.0 is now available! Let’s see what are the main changes in this new release. Hazelcast Client Protocol 2.0 Node.js client now uses Hazelcast Open Binary Client Protocol 2.0, which has a number of enhancements and serialization improvements when compared with 1.x. For the end-user, it means that the client now supports […]