> For the complete documentation index, see [llms.txt](https://docs.silk.us/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.silk.us/learn/get-to-know-silk/silk-cloud-data-platform-overview.md).

# Silk Cloud Data Platform Overview

Learn what the Silk Cloud Data Platform is, what it helps you accomplish, and how its products and data services work together.

The Silk Cloud Data Platform is a software-defined data platform for running mission-critical databases and applications in the cloud. It sits between your workloads and the underlying cloud infrastructure, transforming cloud compute and storage resources into a shared, high-performance data layer.&#x20;

Silk helps organizations:

**Run and scale demanding workloads**

* Run transactional, analytical, and mixed database workloads on shared infrastructure.
* Scale performance and capacity independently as application requirements change.

**Protect and reuse data**

* Provision data copies quickly for development, testing, analytics, AI, and recovery.
* Protect critical data through resilient architecture, snapshots, and replication.&#x20;

**Improve cloud efficiency**

* Reduce storage consumption and cloud costs with built-in efficiency services.
* Manage data consistently across supported cloud environments.

## How the platform works

Traditional cloud storage often ties performance and capacity together. Increasing storage performance can therefore require purchasing more capacity than an application needs — or redesigning the environment as requirements change.

Silk separates the resources that deliver performance from those that provide persistent capacity. You can adjust each resource independently, enabling applications to get the performance and storage they need without unnecessary overprovisioning.&#x20;

The platform pools these resources into a shared data layer that can support multiple databases, applications, and workload types concurrently. Silk automatically manages data placement, protection, and optimization within this layer.&#x20;

## How Silk products work together

The Silk Cloud Data Platform includes several products and management experiences that work together across your data lifecycle.

### Silk DataPods

A Silk DataPod is a virtualized storage environment built on native cloud compute and storage resources. It provides the block storage and data services used by your applications and databases.

Each DataPod separates performance and capacity across three node types:

* **Compute nodes (c.nodes)** deliver high-performance block data services to connected hosts.
* **Media nodes (m.nodes)** organize and protect the DataPod's persistent storage.
* **Data nodes (d.nodes)** store the persistent data managed through the media nodes.

This architecture lets you independently scale performance by adjusting compute resources and scale capacity by adjusting storage resources. DataPods can also be configured for different workload, performance, capacity, or cost requirements.

### Silk Flex

Silk Flex is the orchestration and management interface for the platform. It provides a centralized view of a Silk cluster and its DataPods.&#x20;

Use Flex to:

* Provision and manage DataPods.
* Scale DataPod performance and capacity.
* View resource status and utilization.
* Configure platform-level settings.
* Access additional Silk products and management tools.

A Flex instance manages a cluster containing one or more DataPods.

### SDP Management Console

The SDP Management Console provides detailed storage administration for an individual DataPod. It is integrated with Flex, but operates at a more granular level.&#x20;

Use the console to connect hosts, provision and map volumes, manage snapshots and clones, configure replication, monitor performance, and administer DataPod resources.&#x20;

In practice, Flex manages the wider Silk environment, while the SDP Management Console manages the storage resources and data services within a specific DataPod.&#x20;

### Silk Echo

Silk Echo extends the platform's copy data capabilities to database workflows, creating full-performance database copies in seconds without immediately creating a full physical copy of the source data.

Echo coordinates with DataPods and an Echo Host Agent installed on supported database hosts. The DataPod provides the underlying copy data services, while the Host Agent performs the host- and database-level operations required to prepare and provision usable database copies.&#x20;

These copies can support development and testing, analytics, machine learning, AI, and other secondary workloads without affecting the production database. Echo also automates database-specific activities that would otherwise require coordination across storage, database, and host infrastructure.&#x20;

### Silk Clarity

Silk Clarity provides cloud-based monitoring and analytics for Silk environments. It collects platform telemetry and applies analytics to help Silk and authorized users understand system health, resource utilization, and performance.

Clarity complements the operational views available from Flex and DataPods by supporting broader analysis of platform behavior and trends.

## Built-in data services

Silk data services run within the DataPod and are available to the applications and databases using its storage.

<table data-view="cards"><thead><tr><th align="center"></th><th align="center"></th><th align="center"></th></tr></thead><tbody><tr><td align="center"><h3><i class="fa-ring" style="color:$primary;">:ring:</i></h3><p><strong>Thin provisioning</strong></p></td><td align="center">Allocate physical capacity as data is written instead of reserving the full volume size in advance</td><td align="center"></td></tr><tr><td align="center"><h3><i class="fa-arrows-minimize" style="color:$primary;">:arrows-minimize:</i></h3></td><td align="center"><strong>Inline data reduction</strong></td><td align="center">Use deduplication, compression, and zero elimination to reduce the amount of physical storage consumed.</td></tr><tr><td align="center"><h3><i class="fa-camera" style="color:$primary;">:camera:</i></h3></td><td align="center"><strong>Snapshots</strong></td><td align="center">Create instantaneous point-in-time representations of data without initially duplicating the source data.</td></tr><tr><td align="center"><h3><i class="fa-code-branch" style="color:$primary;">:code-branch:</i></h3></td><td align="center"><strong>Views and Thin Clones</strong></td><td align="center">Turn snapshot data into writable copies that consume additional capacity only as their data changes.</td></tr><tr><td align="center"><h3><i class="fa-clone" style="color:$primary;">:clone:</i></h3></td><td align="center"><strong>Full Clones</strong></td><td align="center">Create independent, fully physical copies when a workload requires them.</td></tr><tr><td align="center"><h3><i class="fa-left-right" style="color:$primary;">:left-right:</i></h3></td><td align="center"><strong>Replication</strong></td><td align="center">Copy snapshot data asynchronously between DataPods to support disaster recovery and other data mobility requirements.</td></tr><tr><td align="center"><h3><i class="fa-chart-network" style="color:$primary;">:chart-network:</i></h3></td><td align="center"><strong>Shared Resources</strong></td><td align="center">Allow multiple applications and workload types to use pooled performance and capacity instead of relying on isolated storage silos.</td></tr></tbody></table>

These services work together to support efficient data provisioning, protection, reuse, and mobility throughout the data lifecycle. For example, an administrator can provision a thin volume, protect it with snapshots, replicate those snapshots to another DataPod, and create writable copies for testing.

## Performance, resilience, and efficiency

Silk continuously adapts how data is handled according to the workload. Its distributed architecture supports high levels of parallelism and is designed to maintain consistent performance across transactional, analytical, and mixed workloads.&#x20;

The platform also protects data across its underlying resources without relying on dedicated idle spares. Redundant components, distributed data and parity, and automated recovery help maintain data availability even when infrastructure components fail.&#x20;

At the same time, shared resources and real-time data reduction reduce the amount of cloud infrastructure needed to support production and secondary workloads.&#x20;

Together, these capabilities give you a single data platform for running, managing, protecting, and reusing mission-critical data in the cloud, while retaining control over performance, capacity, resilience, and cost.

***

{% hint style="info" %}
**See Silk in action**

Learn how the Silk Cloud Data Platform can help you run mission-critical workloads with greater performance, flexibility, and cloud efficiency.

<a href="https://silk.us/resources/demos/" class="button primary">Request a Demo</a>
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.silk.us/learn/get-to-know-silk/silk-cloud-data-platform-overview.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
