Viridian Serverless Clusters

Serverless is a managed cloud service that offers a pay-as-you-go pricing model. Serverless clusters auto-scale to provide the resources that your application needs. You pay only for the resources that your application consumes.

Serverless means that Hazelcast manages the cloud infrastructure for you. Each Viridian Serverless cluster is an independent deployment of Hazelcast Platform in a Kubernetes container. This design guarantees resource isolation, prevents resource stealing, and provides isolated network access.

Beta Release

Viridian Serverless is in beta while we continue to add new features.

Despite its beta state, you can use Viridian Serverless production clusters for production applications.

Viridian Serverless Cluster Types

Viridian Serverless clusters come in two types:

  • Development: Capped storage. You can store at most 1 GiB of data.

  • Production: Uncapped storage. The cluster scales as you add or remove data.

Development Clusters

Development clusters are for fast, iterative development while you prototype your application.

Development clusters have the following limitations:

  • Maximum 1 GiB of storage

  • Only a single member

  • No cluster scaling

  • No data backups

  • No cluster data persistence

When a development cluster restarts for any reason, you lose cluster data such as maps and cluster-side modules.

You cannot convert a development cluster to a production cluster.

Production Clusters

Production clusters are for applications that have already been tested and are ready to be deployed in real-world scenarios.

Production clusters automatically scale out and in, depending on the amount of resources you use.

Your cluster data is persisted on disk so that you can pause and resume your clusters when you want, without losing your data. Cluster data is persisted in the following scenarios:

  • Automatic backups once per day.

  • When a production cluster restarts for any reason.

  • You trigger manual backups.

What is cluster data?

Cluster data includes the following:

  • Configuration settings

  • Cluster-side modules

  • Jobs

  • Map and JCache data structures

Backups

By default, data in production clusters is backed up on one other member in the cluster.

Although you can configure some data structures with a custom backup count, the effective backup count is limited by the number of members in your cluster. For example, if you configure a map with 5 backups, but your cluster has only 2 members, you will have one effective backup. You cannot scale out Viridian Serverless clusters. If you add enough data to the cluster so that it automatically scales up the number of members, more backups will be added, up to your configured count of 5.

Restrictions on Free Viridian Serverless Clusters

Development and production clusters are stopped when both of these conditions are true:

  • You don’t connect to the cluster for 24 hours.

  • You don’t have a payment method set up for your Hazelcast Viridian account.

If you’re using a production cluster, Hazelcast saves your cluster data so that you can resume the cluster at a later time.

If you’re using a development cluster, all cluster data is lost after the cluster is stopped.

Pricing for Viridian Serverless Clusters

You pay only for what you store in RAM. Any data that is stored on disk or in backups is free of charge. As a result, 'storage' is synonymous with RAM in Viridian Serverless clusters.

Viridian Serverless clusters are billed monthly only for the amount of used storage. The first 2 GiB of storage in your account is free. If you use more than 2 GiB across all your clusters, you are charged $0.10 per hour for every additional GiB of used storage, not including the first 2 GiB.

As well as the data that you add to data structures such as maps, you are charged for any additional memory usage, excluding backups. Backups are free. Additional memory usage may include the following:

  • Indexes that you create

  • Stateful jobs

  • Serialization overhead

For example, the HazelcastJsonValue serializer includes metadata to allow the cluster to query JSON fields and values. You are charged for this metadata. As a result, the amount of used memory in your cluster may be more than the amount of data that you added to a data structure.

Billing Examples

You have an empty cluster. You ingest 3 GiB of data into the cluster, run a query, and remove the data. For one hour, your cluster stored 3 GiB data, and then the cluster remained empty for the rest of the month. You are billed for 1 GiB for one hour, which is $0.10.

These examples show the cost per month of two clusters in the same account:

Cluster Used storage Time Cost

1

2 GiB

Unlimited

Free

2

10 GiB

10 minutes

10 GiB * 10/60 * 0.1 = $0.16

Supported Functionality

Use this table to learn what is supported in Viridian Serverless clusters:

Functionality Production clusters Development clusters

Supported

Supported

Supported

Supported

Supported

Supported

Supported

Supported

Supported

Supported

Manually scale the cluster

Not supported (autoscales)

Not supported (autoscales)

Auto scaling

Supported (always enabled)

Not supported

Supported

Supported

Supported

Supported

Edit map configuration

Not Supported

Not Supported

Delete data structure configuration

Not supported

Not supported

Automated daily backups

Supported (always enabled)

Not supported

Supported

Not supported

Supported

Supported

Supported

Supported

Supported

Not supported

Choose a version of Hazelcast member software

Not supported (always uses the latest version)

Not supported (always uses the latest version)

Integrate with an external logging service

Not supported

Not supported

VPC peering

Not supported

Not supported

AWS PrivateLink

Not supported

Not supported