Platform Feature Access
This page explains how Smart DIH and Smart Cache features are accessed.
Everything in Kubernetes
An open-source container orchestration system for automating software deployment, scaling, and management. can be installed using Helm.
| Operation | Access | Environment | Notes |
|---|---|---|---|
| Hosts Management |
Kubernetes Non-Kubernetes Non-Kubernetes Non-Kubernetes |
Monitoring the health of the hosts |
|
| Containers | Admin API | Non-Kubernetes | Managing the running processes (restart, statistics, etc.) |
| Administration | SpaceDeck | Kubernetes | Authentication, authorization, roles and resource management. |
| Management of Data Sources | SpaceDeck | Kubernetes | |
| Management of Pipelines | SpaceDeck | Kubernetes | |
| Management of Spaces | SpaceDeck |
Kubernetes Non-Kubernetes Both Both Both Non-Kubernetes |
SpaceDeck GigaSpaces intuitive, streamlined user interface to set up, manage and control their environment. Using SpaceDeck, users can define the tools to bring legacy System of Record (SoR) databases into the in-memory data grid that is the core of the GigaSpaces system.: New Space Where GigaSpaces data is stored. It is the logical cache that holds data objects in memory and might also hold them in layered in tiering. Data is hosted from multiple SoRs, consolidated as a unified data model. basic control including partitions and redundancy. Ops Manager: Advanced configuration of the Space and secure space |
| Management of Data Access Services (PUs) | WEB-UI |
Non-Kubernetes Both Both Both Non-Kubernetes |
Manual: Secure Space config proxy When using Kubernetes this is achieved Helm commands or Ops Manager |
| Data Access Micro-Services (Low-Code) | SpaceDeck | Kubernetes | |
| Data Gateway | Ops Manager |
Both Non-Kubernetes |
Provides the ability to connect to the Space using other data tools, for example, DBeaver. |
| Data Query | SpaceDeck |
Kubernetes Non-Kubernetes |
|
| Stream SQL | SpaceDeck |
Kubernetes | Provides the ability to implement a low code (SQL) approach to define and operate with ad-hoc data flows, such as read from Kafka Apache Kafka is a distributed event store and stream-processing platform. Apache Kafka is a distributed publish-subscribe messaging system.
A message is any kind of information that is sent from a producer (application that sends the messages) to a consumer (application that receives the messages).
Producers write their messages or data to Kafka topics. These topics are divided into partitions that function like logs.
Each message is written to a partition and has a unique offset, or identifier. Consumers can specify a particular offset point where they can begin to read messages. and write directly to Space or read from one Kafka topic and write to another Kafka topic. |
| Operation | Access | Environment | Notes |
|---|---|---|---|
| Hosts Management |
Non-Kubernetes Non-Kubernetes Non-Kubernetes Kubernetes |
Monitoring the health of the hosts |
|
| Containers |
Non-Kubernetes |
Managing the running processes (restart, statistics, etc.) | |
| Management of Spaces |
Non-Kubernetes Both Both Both Non-Kubernetes Kubernetes |
Ops Manager: Advanced configuration of the Space and secure space. | |
| Management of Data Access Services (PUs) |
Non-Kubernetes Both Both Both Non-Kubernetes |
||
| Data Gateway |
Both Non-Kubernetes |
Provides the ability to connect to the Space using other data tools, for example, DBeaver. | |
| Data Query |
Non-Kubernetes Kubernetes |