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.
We offer Hazelcast IMDG and Hazelcast Jet with different configuration and deployment options to fit your business needs. Click on the buttons below to find the right solution for you. Then compare service options to find the subscription plan that best meets your requirements. Need help deciding? Our sales experts are just a click away. Or call us at +1 (650) 521-5453.
Hazelcast IMDG Enterprise
Hazelcast Jet Enterprise
Support Window Service-level Agreement
Quarterly Review of Feature Requests
Quarterly Review of the Hazelcast Roadmap
Email, IM, phone support contacts
Access to Hot Fix Patches
Simulation of your production Hazelcast profile for upgrade/config change verification
Black Duck Clean IP Report
A Hazelcast node is a JVM on which an instance of Hazelcast is in operation: • There is no charge per CPU or CPU core. • The charge is based on the number of Members (Hazelcast server nodes), including Lite Members. • The minimum cluster size is 3 nodes. Which nodes count as Hazelcast nodes? • The node count is calculated as the number of JVMs that are running a Hazelcast instance. An instance may be run on its own from the command line (server) or started from within an application server (embedded). • It is also possible to run multiple Hazelcast instances in one JVM. Multiple instances running in one JVM count as one node. • A production node or hot-standby node or warm-standby node is a JVM where the Hazelcast software is running. These are counted. • Non-production nodes include cold standby (power is off), or QA, Test and Dev nodes. These are not counted.
We can help you decide which option is best for you.
All fields marked * are required
Whether you're interested in learning the basics of in-memory systems, or you're looking for advanced, real-world production examples and best practices, we've got you covered.