Skip to content

Object Storage

Welcome to the realm of edge-native object storage in Taubyte. Just like any other component of a Taubyte-based cloud computing network, object storage is designed with serverless, decentralized principles, paving the way for highly scalable, reliable, and resilient storage solutions.

Object storage is a critical piece of the puzzle in the world of distributed computing. Its purpose? To store, retrieve, and update a vast sea of unstructured data. Think of it as a giant, never-ending vault that keeps everything from documents, photos, and videos, to backups, logs, and even entire static websites. It’s your go-to place for handling data that doesn’t fit neatly into a tabular format.

Here’s what sets Taubyte object storage apart:


Whether you’re dealing with a handful of documents or storing millions of high-resolution images, Taubyte’s object storage can handle it with grace. It scales on-demand to accommodate your growing storage needs, ensuring you never run out of space.

Serverless and Decentralized

Taubyte’s object storage is not tied to a central server, nor does it need a server to manage its operations. The storage units are distributed across the network, each one contributing to a robust, fail-safe storage solution that can withstand network issues, physical damage, and even cyber threats.

Provisioning for Specific Use Cases

Here’s where things get interesting. Object storage resources in Taubyte can be turned into templates by enabling regex matching. This allows for the provisioning of unique storage instances, each tailored to a specific use case. So if you’ve got a bunch of IoT devices or a collection of Web3 wallets, each one can have its own dedicated object storage, customized to its unique needs.

Consistency Across a Distributed Network

Taubyte’s object storage leverages Conflict-free Replicated Data Type (CRDT), a consensus mechanism that ensures all storage units (nodes) in the network maintain a consistent state, despite being geographically distributed. It’s an ingenious way to resolve conflicts without the need for a central server. And we’re not stopping at that; the future holds plans for integrating other consensus mechanisms such as Practical Byzantine Fault Tolerance (PBFT) to cater to varying demands.

To illustrate, here’s an example of an object storage configuration in Taubyte:

id: Qmckzdx5DKRnBQ9yXCqSxu9xQhzuPfK1zMaV1vA3NiRmZ7
description: ''
tags: []
match: '/drive/0x[a-fA-F0-9]{1,}'
useRegex: true
    network: all
    versioning: true
    size: 1GB

Components of the configuration file are explained below:

  • id: The unique identifier for the object storage.
  • match: This defines what triggers match the object storage resource. In this case it will create a storage bucket per wallet address.
  • useRegex: This flag indicates whether regex (regular expression) matching is used for the object storage path. If true, the object storage resource behaves like a template, allowing for provisioning object storages specifically for certain use cases.
  • object: This section specifies the object storage parameters.
    • versioning: This flag indicates that files/objects are versioned not replaced