Hazelcast Cloud is an enterprise-grade in-memory computing platform deployed and managed by the Hazelcast CloudOps team. The service
is powered by Hazelcast IMDG Enterprise HD and leverages widely adopted technologies, such as Docker and Kubernetes, to provide dynamic orchestration and containerization. Hazelcast Cloud supports applications developed in some of the most common languages, including Java, Node.js, Python. Go, and .NET.
Hazelcast Cloud delivers enterprise-grade Hazelcast software in the cloud, deployed as a fully managed service. Leveraging over a decade of experience and best practices, Hazelcast Cloud delivers a high-throughput, low-latency service that scales to your needs while remaining simple to deploy. If you’re considering moving to the Cloud, or are looking for an easy ramp on deploying in-memory technology, this white paper on migrating in-memory to the cloud is an informative and helpful resource.
Setting up servers and configuring software can get in the way of the problems you are trying to solve. With Hazelcast Cloud we take all of those pain points away.
Join this webinar on April 11th at 8:00 am PT / 11:00 am ET / 4:00 pm GMT to learn how you can instantly fire up and then work with Hazelcast Cloud from anywhere in the world. With our auto-generated client stubs for Java, Go, Node.js, Python and .NET, we can have you connected and coding in less than a minute!
Get a 30-day free trial.
Get started today with the
industry’s leading in-memory computing platform.
The in-memory speed you count on, with the convenience and scalability of cloud.
This benchmark tests the write and read performance of the Hot Restart Store, introduced in Hazelcast® Enterprise HD 3.6. All benchmarks test the performance of one Hazelcast member running on a physical server. As the Hot Restart Store is local to each member, performance is linearly scalable.
The Hazelcast Hot Restart Store is novel in that it is only ever written to when the cluster is operational. It is never read from. It is only read during start up where we read the entire store into memory before enabling operations. All operational reads are therefore always to RAM.
There are two questions on performance that are important: write performance and read performance.
All tests were performed on HP ProLiant servers running RHEL 7
Two common types of media were tested: 10k HDD and Solid State Drives.
Tests were performed using Hazelcast Simulator: