Skip to content

Instantly share code, notes, and snippets.

@hd1801

hd1801/storage_tiers.md

Forked from CMCDragonkai/storage_tiers.md
Created January 8, 2024 16:48
Download ZIP

Revisions

  1. @CMCDragonkai CMCDragonkai revised this gist Dec 20, 2018. 1 changed file with 1 addition and 0 deletions.
    1 change: 1 addition & 0 deletions storage_tiers.md
    View file
    Original file line number Diff line number Diff line change
    @@ -30,6 +30,7 @@ Networked Variant:

    * NFS
    * Ceph
    * IPFS

    ## Object Storage

  2. @CMCDragonkai CMCDragonkai revised this gist Dec 20, 2018. 1 changed file with 1 addition and 1 deletion.
    2 changes: 1 addition & 1 deletion storage_tiers.md
    View file
    Original file line number Diff line number Diff line change
    @@ -15,7 +15,7 @@ This is what operating systems "hosts" require ([at least to boot](https://netwo

    Networked Variant:

    * iSCSI
    * iSCSI (AWS offers Storage Gateway, a cloud-managed iSCSI target)
    * ATA over Ethernet

    ## Filesystems
  3. @CMCDragonkai CMCDragonkai revised this gist Dec 20, 2018. 1 changed file with 1 addition and 1 deletion.
    2 changes: 1 addition & 1 deletion storage_tiers.md
    View file
    Original file line number Diff line number Diff line change
    @@ -11,7 +11,7 @@ At the bottom we have block devices supplied by HDDs and SSDs. These use a proto

    They are presented as block devices to the operating system. Use `lsblk` to see all the connected block devices.

    This is what operating systems "hosts" require (at least to boot).
    This is what operating systems "hosts" require ([at least to boot](https://networkboot.org/)).

    Networked Variant:

  4. @CMCDragonkai CMCDragonkai revised this gist Dec 20, 2018. 1 changed file with 4 additions and 0 deletions.
    4 changes: 4 additions & 0 deletions storage_tiers.md
    View file
    Original file line number Diff line number Diff line change
    @@ -11,6 +11,8 @@ At the bottom we have block devices supplied by HDDs and SSDs. These use a proto

    They are presented as block devices to the operating system. Use `lsblk` to see all the connected block devices.

    This is what operating systems "hosts" require (at least to boot).

    Networked Variant:

    * iSCSI
    @@ -22,6 +24,8 @@ Filesystems backed by some set of block devices. They present a POSIX filesystem

    This is what the marketing term of "Block Storage" usually refers to.

    This is what containers require.

    Networked Variant:

    * NFS
  5. @CMCDragonkai CMCDragonkai created this gist Dec 20, 2018.
    40 changes: 40 additions & 0 deletions storage_tiers.md
    View file
    Original file line number Diff line number Diff line change
    @@ -0,0 +1,40 @@
    # Storage Tiers

    1. Block Devices
    2. Filesystems
    3. Object Storage
    4. Application Domain

    ## Block Devices

    At the bottom we have block devices supplied by HDDs and SSDs. These use a protocol like SCSI or ATA or SAS or SATA.

    They are presented as block devices to the operating system. Use `lsblk` to see all the connected block devices.

    Networked Variant:

    * iSCSI
    * ATA over Ethernet

    ## Filesystems

    Filesystems backed by some set of block devices. They present a POSIX filesystem interface that most Unix applications expect.

    This is what the marketing term of "Block Storage" usually refers to.

    Networked Variant:

    * NFS
    * Ceph

    ## Object Storage

    These systems abstract filesystem semantics into a simpler key-value semantics. Every object has a key and a value. Amazon S3 is a typical example.

    Almost all object storage systems are intended to be served over a network.

    ## Application Domain

    These present a more domain-specific stateful interface. But any application which maintains "memory" in some form will present some interface to storage.

    Almost all application domain state are intended to be served over a network.