Cloud Sizing

Lobster Cloud is available in multiple editions, each designed for a specific business scope and availability requirement. This page covers the technical specifications for all sizings, an overview of dimensioning options, and the available upgrade paths.

Each edition is available in one or more sizing options. The sizing defines the compute resources (vCPU, RAM) and storage capacity assigned to your system.

Lobster Data Platform server

The Base System is the standard deployment option for Lobster Cloud and is designed for environments with standard availability requirements. It is based on a single-node setup without cross-component redundancy and guarantees a monthly availability of 99.0%. For environments with higher availability requirements, we recommend the High Availability Architecture (99,9%)

Base Systems

DMZ and DEV servers

Java heap allocation

The specified percentage defines the maximum share of the server's total RAM allocated to the Java Virtual Machine (JVM) as heap memory. For example, a size M instance with 16 GB RAM and a 75% allocation provides the JVM with up to 12 GB of heap space. The remaining memory is reserved for the operating system and system-level processes and is not available to the JVM.

Summary

Overview

Sizing Mapping

Use case suitability by sizing

Important

The scenarios and sizing specifications presented here are reference values for guidance purposes only. The Lobster DATA Platform is highly flexible and can be adapted to a wide range of requirements. Since every customer has unique workloads and conditions, these values cannot cover every use case universally.

Upgrade paths

Lobster Cloud provides a clear upgrade path so your environment can grow with your business. All upgrades will be carried out by Lobster after the order has been placed.

Size Upgrades

Note

DMZ and DEV servers cannot be resized independently. Their sizing is fixed to size S or M.

Architecture migration to high availability

Customers with standard systems can migrate to a high-availability architecture for an additional charge.

Storage Extension Packages

If your standard storage capacity is not sufficient, you can extend it with the following packages. Storage extensions always apply to both your production and test environments.

High availability architecture

The High Availability (HA) architecture is a redundant multi-node setup that absorbs the failure of individual components without interrupting ongoing operations. Redundancy across all critical layers, from the DMZ servers through the database to the shared file system, ensures a monthly availability of 99.9%.

Standard HA Production system components

Note

A HA setup can have a total of two working nodes.

Standard HA Test System Components

Note

The test system can be extended to a full HA configuration by adding a second DMZ server and a Working Node. A HA setup can have a total of two working nodes.

High volume file system (FSx)

For customers handling large numbers of small files (under 100 KB), the standard EFS file system can be replaced with FSx for NetApp ONTAP. This upgrade delivers sub-millisecond latencies, provisioned IOPS, and significantly faster individual file operations. The High-Volume upgrade requires Cloud Sizing L, XL or XXL and includes 1 TB for each test and production environment.

Recommendation

If your workload involves frequent processing of files smaller than 100 KB, or if you require sub-millisecond response times, the High Volume option is recommended. For workloads primarily involving larger files, the Standard Volume provides sufficient performance.

Change History

Note

Changes to sizing and disk capacities are not applied retroactively to existing installations. The terms specified in the respective offer or order agreement continue to apply.