Cache-as-a-Service (CaaS)

See Hazelcast in Action

Master intelligent applications with Hazelcast unified real-time stream processing platform.

Introduction

A cache is an important component of any application. In-memory caching can eliminate the bottlenecks for data access and processing to provide predictable latency and fast response time as an application’s user base grows. Implementing a cache-as-a-service across the organization enables multiple applications to access a managed in-memory cache rather than slow disk-based databases.

The Hazelcast approach to cache-as-a-service

By using Hazelcast Platform as a cache-as-a-service, developers can separate the caching layer from the application layer. With cache-as-a-service, you can add caching to any application without worrying about the cache implementation.

Hazelcast provides a cache-as-a-service for scalable, reliable, and fast caching. Applications can use Hazelcast Platform as a side-cache to their database or place the database in-line behind the caching service.

Hazelcast Platform Cache-As-A-Service Cluster
Hazelcast Platform Cache-As-A-Service Cluster

Why Hazelcast

Fast, in-memory performance, ease of development, and scalability

Hazelcast Platform provides a number of features that make it ideal as a cache-as-a-service. Hazelcast Platform 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 it 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

Cloud-native architecture

Enables the elasticity to grow or shrink as needed.

Built-in security

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.

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 Platform automatically load and store data from a database.