[HN Gopher] The disaggregated write-ahead log (2023)
       ___________________________________________________________________
        
       The disaggregated write-ahead log (2023)
        
       Author : carlsverre
       Score  : 52 points
       Date   : 2024-02-06 22:59 UTC (1 days ago)
        
 (HTM) web link (blog.schmizz.net)
 (TXT) w3m dump (blog.schmizz.net)
        
       | epaulson wrote:
       | This sentence is doing a lot of work: "Hypothetical S2 does a bit
       | more to simplify the layers above - it makes leadership above the
       | log convenient with leases and fenced writes."
       | 
       | It'd be awesome to have a bit more transactional help from S3.
       | You could go a long way with 'only update this object if the
       | ETags on these other objects are still the same'. I know AWS
       | doesn't want to turn S3 into a full database but some updates you
       | just can't do without having a whole 2nd service running
       | alongside to keep track of the states of your updates.
        
         | shikhar wrote:
         | Agreed, both Google Cloud Storage and Azure Blob Storage
         | support preconditions. Azure even has leases. S3 is for better
         | or worse the common denominator for systems layering on top of
         | object storage.
        
       | ditsuke wrote:
       | Remember reading this one just last month!
        
       | bvrmn wrote:
       | Generic robust replicated log would be nice to have. For two
       | products I've implemented leaderless oplog to back application
       | level replication to sync not only database changes but also
       | configuration files and other needed data. Works like a charm.
        
         | HammadB wrote:
         | Curious - what was the specific leaderless replication
         | strategy?
        
       ___________________________________________________________________
       (page generated 2024-02-07 23:00 UTC)