[HN Gopher] Show HN: SlateDB - An embedded storage engine built ...
       ___________________________________________________________________
        
       Show HN: SlateDB - An embedded storage engine built on object
       storage
        
       SlateDB is an embedded storage engine built as a log-structured
       merge-tree. Unlike traditional LSM-tree storage engines, SlateDB
       writes data to object storage (S3, GCS, ABS, MinIO, Tigris, and so
       on). Leveraging object storage allows SlateDB to provide bottomless
       storage capacity, high durability, and easy replication. The trade-
       off is that object storage has a higher latency and higher API cost
       than local disk.  To mitigate high write API costs (PUTs), SlateDB
       batches writes. Rather than writing every put() call to object
       storage, MemTables are flushed periodically to object storage as a
       string-sorted table (SST). The flush interval is configurable.  To
       mitigate write latency, SlateDB provides an async put method.
       Clients that prefer strong durability can await on put until the
       MemTable is flushed to object storage (trading latency for
       durability). Clients that prefer lower latency can simply ignore
       the future returned by put.  To mitigate read latency and read API
       costs (GETs), SlateDB will use standard LSM-tree caching
       techniques: in-memory block caches, compression, bloom filters, and
       local SST disk caches.
        
       Author : riccomini
       Score  : 14 points
       Date   : 2024-08-14 19:17 UTC (3 hours ago)
        
 (HTM) web link (github.com)
 (TXT) w3m dump (github.com)
        
       | Reubend wrote:
       | It's a very very cool idea, but I'm still not clear on the main
       | benefits.
       | 
       | Bottomless storage: yes, but couldn't you theoretically achieve
       | this with plenty of cloud DB services? Amazon Aurora goes up to
       | 128 TB, and once your DB gets to that size, it's likely that you
       | can hire some dedicated engineers to handle more complicated
       | setups.
       | 
       | High durability: yes, but couldn't this be achieves with a
       | "normal" DB that has a read replica using object storage, rather
       | than the entire DB using object storage?
       | 
       | Easy replication: arguably not easier than normal replication,
       | depending on which cloud DB you're considering as an alternative.
        
       ___________________________________________________________________
       (page generated 2024-08-14 23:01 UTC)