About Silk
Silk offers the flexibility and high performance that organizations need to leverage the public cloud. The Silk Data Virtualization Platform is a combination of tested and packaged software and services. Silk provides a rich set of data services, machine learning, analytics, and policy-based automation and orchestration.
Use this guide to learn about the prerequisites to successfully deploy Silk onto your instance of Microsoft Azure.
Refer to the following guides for more information about the prerequisites, steps involved, architecture, security, and networking requirements to successfully deploy Silk onto your instance of Microsoft Azure.
- Deploying Silk – Overview & Background
- How to Deploy Silk
- Architecture Requirements to Deploy Silk
- Security Requirements to Deploy Silk
- Networking Requirements to Deploy Silk
Deploying Silk – Overview & Background
Silk System Overview
The Silk Data Virtualization Platform sits between your cloud storage infrastructure and cloud databases. Silk uses a unique architecture to allow you to maximize your storage capacity on the cloud while providing accelerated performance.
Silk Flex
Silk Flex is our data orchestration platform for managing resources in the public cloud. Silk Flex delivers an on-demand ability to compose, optimize, manage, and decommission resources as needed to support application Service Level Agreements (SLAs) from within the Silk Data Virtualization Platform. Silk Flex orchestrates cloud resources as new workloads emerge, move, and evolve over time.
Silk VisionOS
Silk VisionOS provides a rich set of tools to monitor and manage the Silk Data Virtualization Platform. These management services do not require additional hardware resources.
Silk Cloud Architecture
Refer to Figure 1 below for the Silk Architecture in Azure.
Figure 1: Silk Architecture in Azure
Silk Data Pod (SDP)
The Silk public cloud architecture consists of the following:
- c.node
- m.node
A Silk Data Pod contains a minimum of two (2) c.nodes and one (1) m.node.
c.node
The c.node is the compute/controller node. A minimum of two (2) c.nodes is required to build a Silk Data Pod (SDP) and for redundancy.
Note: You can scale to a maximum of eight (8) c.nodes in Microsoft Azure.
m.node
The m.node is the media node that stores your data and applications. At least one (1) m.node is required for data capacity. Each m.node is made up of multiple d.nodes based on type and configuration (Table 1).