The Hazelcast approach to cache-as-a-service
The Hazelcast advantage
Fast, in-memory performance, ease of development, and scalability
Hazelcast provides a number of features that make it ideal as a cache-as-a-service. Hazelcast always stores and processes data in-memory for blazing-fast performance. It enables developers to leverage the cache with only minor modifications for many of their applications written in common languages. And Hazelcast elastically scales to handle more data and more user load thanks to its cloud-native architecture.
Features that make Hazelcast an optimal cache-as-a-service
Enables the elasticity to grow or shrink as needed.
Lets you protect sensitive data with access controls, thus simplifying the multi-tenant requirements of cache-as-a-service.
Native memory storage
Avoids garbage collection and provides predictable low latency across different applications without affecting each other.
Native client libraries
Java, .NET, and C++ applications can use native client libraries to access the cache. For other languages, applications can use Hazelcast REST and Memcached interfaces.
Hazelcast Management Center
Enables you to monitor cache server nodes, connected clients, and used caches. It provides notifications when cluster management operations take too long, making it easy to identify performance and stability issues.
Enables you to replicate the cache across multiple data centers to distribute the load to geographically remote users or to support disaster recovery strategies.
Standard APIs in JCache and Map interfaces
Hazelcast provides two standard APIs in its JCache and Map interfaces. JCache is standard for JSR 107 and the Map interface is based on java.util.Map. Developers can use MapStore and CacheStore, respectively for Map and JCache, to make Hazelcast automatically load and store data from a database.