ZebClient
Zebware.comCustomer Portal
  • ZebClient Documentation
  • Product Overview
    • Introduction to ZebClient
    • Functional Overview
    • Product Components
    • Data Flows
    • Data Striping
  • USE CASES
    • ZebClient Analytics
      • Architecture
        • Data Pipeline
        • Data Storage
        • Consumption
      • Deploy a ZebClient Advanced Cluster
        • Step 0 - Setup
      • FAQ
  • Planning & Getting Started
    • How to Choose your Deployment Mode
    • Deployment Modes and Tuning
    • Performance
    • License
    • Order Your ZebClient License
    • Pricing
  • Installation
    • Types of Installations
    • Guided Installation
      • ZebClient with Azure Blob Storage
        • Defining Backend with Azure Blob Storage
        • Mounting ZebClient with Azure Blob Storage
      • ZebClient with AWS S3
        • Defining Backend with AWS S3
        • Mounting ZebClient with AWS S3
      • Mount Additional Agent Node
    • Kubernetes
      • Azure Quickstart Guide
      • ZebClient CSI
      • ZebClient Helm
      • ZebClient Terraform
    • Virtual Machines
      • Azure Installation Guide
        • Installing Using Terraform
        • Uninstalling Using Terraform
    • Checking Installation
    • Running First Test
  • Management HOW-TOS
    • Add a New Agent VM into an Existing Cluster
    • Retrieve Cluster Log Files
    • CloudFormation Deployments
      • Understanding our CloudFormation Template
      • Uninstalling Using CloudFormation
    • Command-line Interface
  • Operations & Monitoring
    • Importing Your Data
    • Inlets
      • Data from External S3 Bucket
    • System Recovery Guide
      • Restore KeyDB Backup from S3
    • Port a Deploy
    • Add Resources to a Cluster
      • Add Application Node to Existing Machine (Manually)
      • Add Application Node to Existing Machine (via zc-cli)
      • Add New Application Node
      • Add Jumpbox
    • Verifying License Validity
    • Monitoring Your ZebClient Cluster with Netdata
Powered by GitBook
On this page
  • Performance
  • Data Protection
  • Data Privacy
  1. Product Overview

Data Striping

PreviousData FlowsNextZebClient Analytics

Last updated 1 year ago

There are a number of important aspects of ZebClient that are enabled through data striping; the mechanism by which ZebClient actively manages the placement of data shards across the ZebClient Acceleration Engine cluster. The code by which ZebClient performs this active placement is a highly mathematically optimized algorithm that ensures conformance to a K+M configuration of data and parity shards.

Performance

The first is performance. With data striped across ZebClient Acceleration Engine, data will be retrieved in parallel from the nodes containing the relevant data. This effect is especially powerful when retrieving a large amount of data in a sequential fashion and where block sizes are relatively large. This configuration provides ZebClient with the ideal conditions to make optimal use of the striping effect and serves to avoid access hot spots that would otherwise degrade performance.

Data Protection

The second important aspect is data protection. With data distributed evenly and redundantly across the ZebClient Acceleration Engines, shards are placed to ensure there is no one part of the system that can fail and affect the rest of the system. This is a critical part of any file system and one where a parallel file system such as ZebClient can ensure a high level of redundancy without the typical compromises of scalability, capacity, or performance.

Data Privacy

The third is data privacy. With shards striped across Acceleration Engines, it becomes straightforward for ZebClient to store this data in object storage across different regions or even different object storage providers. This functionality enables a data privacy use case where there might be sensitivity in using public cloud suppliers.