The cache instance that holds data objects in memory and might also hold them in layered in tiering.

A set of methods used to read, write, take, and register for notification on objects that are stored in the Space. Execute allows sending Tasks to be executed within the Space. Read and Take criteria can be specified via a query or a template (an example object).

A service performs operations with the underlying data. There are several types of Services:

• Stateful PU/Service - space containing data and also might embed services related to that space's data.

• Stateless PU/Service - There are built-in services as mirror wan-GW, data-GW. In addition, there are custom services which are customer driven.

• Client Services - applications that interact with spaces.  In Smart DIH these include low-code micro services.

Stateless services are shown in UI tools (ops-ui/SpaceDeck).

Metrics of stateless services are managed.

If running in a Kubernetes environment, client services can use spring boot and enjoy Kubernetes direct management and manage their own metrics directly.

When running in Service Grid, the SLA of all services is managed by the Service Grid.

A combination of clients and/or an embedded Space instance. This is the fundamental unit of deployment in the data grid. The Processing Unit itself is typically deployed onto the cluster. When a Processing Unit is deployed, a Processing Unit instance is the actual runtime entity.  The number of PU instances in a PU will be deployed according to the SLA defined.

A deployable package containing one or more services. In the GigaSpaces context, it usually acts as a client that interacts with other Processing Units by utilizing the messaging capabilities of the Space.

A deployable, independent, scalable unit that is the building block of Space-Based Architecture. A client application (which can also be other Processing Units) write objects to the Space, and the Processing Unit that contains this Space consumes these objects or is notified about them and triggers related services.

Each partition holds a different subset of the objects. When the objects are written to this data grid, they are routed to the proper partition according to a predefined attribute in the object that acts as the routing index. There is an exception for routing which duplicates data over all the partitions using a Broadcast Table. See Broadcast Objects for more information.

The mechanism that is in charge of routing the objects into and out of the corresponding partitions. The routing is based on a designated attribute inside the objects that are written to the Space, called the Routing Index.

A partitioned data grid, with backup for each partition. Each data grid instance (partition) holds a different subset of the objects in the data grid, and replicates this subset to its backup instance.