[HN Gopher] AlloyDB for PostgreSQL
       ___________________________________________________________________
        
       AlloyDB for PostgreSQL
        
       Author : mhoad
       Score  : 20 points
       Date   : 2022-05-11 19:41 UTC (3 hours ago)
        
 (HTM) web link (cloud.google.com)
 (TXT) w3m dump (cloud.google.com)
        
       | drewda wrote:
       | I'd be curious to hear if anyone can speak to how this compares
       | to:
       | 
       | - Citus columnar storage for Postgres, now owned by Microsoft
       | 
       | - Amazon Aurora PostgreSQL compatibility layer
       | 
       | - Timescale hypertables
        
         | mattashii wrote:
         | both of the mentioned features from Citus and Timescale are
         | extensions on PostgreSQL, so they do not alter the way storage
         | works in PostgreSQL in any meaningful manner.
         | 
         | AlloyDB Seems better compared to Aurora, and they seem to share
         | a significant amount of design principles with log-shipping,
         | but now with an extra caching layer at or near the database
         | instance.
         | 
         | As for the 'columnar' features, from the release post it seems
         | like AlloyDB does not specifically store the data at rest in a
         | columnar format, but transforms the rows into columnar for
         | analytical queries (but I'm not sure about that). That indeed
         | improves performance of certain classes of queries.
        
       | Ataraxy wrote:
       | Unfortunately this seems to be expensive for arbitrary use.
        
       ___________________________________________________________________
       (page generated 2022-05-11 23:02 UTC)