[HN Gopher] Neki - sharded Postgres by the team behind Vitess
       ___________________________________________________________________
        
       Neki - sharded Postgres by the team behind Vitess
        
       Author : thdxr
       Score  : 116 points
       Date   : 2025-08-11 18:03 UTC (4 hours ago)
        
 (HTM) web link (planetscale.com)
 (TXT) w3m dump (planetscale.com)
        
       | shoeb00m wrote:
       | Looks like there is two ongoing vitess for postgres projects.
       | Hopefully this competition leads to a better postgres ecosystem.
       | 
       | https://supabase.com/blog/multigres-vitess-for-postgres
        
         | qaq wrote:
         | Supabase also working on OrioleDB
        
           | eatonphil wrote:
           | OrioleDB is not about sharding, it's about the storage layer.
        
             | qaq wrote:
             | I did not claim OrioleDB is about sharding. It was just an
             | observation that Supabase is contributing to Postgres
             | ecosystem through multiple projects.
        
               | selfhosttoday wrote:
               | they likely said that because the context is "vitess for
               | postgres projects" and OrioleDB is not "vitess for
               | postgres"
        
         | n2d4 wrote:
         | There is also pgdog by the author of pgcat: https://pgdog.dev
        
         | dangoodmanUT wrote:
         | It gets more spicy when you realize the founder of vitess, also
         | the founder of planet scale, left planet scale to build this at
         | supabase
        
       | hubertzhang wrote:
       | Does Neki still need sharding key in query, just like Citus?
        
       | ozgrakkurt wrote:
       | Is anyone working on replacing postgres?
       | 
       | Feels like it might be very useful since a lot of new
       | technologies came out since spinning disks.
        
         | erpellan wrote:
         | If you look at the changes that have been made to Postgres, and
         | continue to be made, the answer is yes.
         | 
         | The Postgres team is working on replacing Postgres. With even
         | better Postgres.
        
           | bddicken wrote:
           | The Postgres team incorporating io_uring into PG 18 is a good
           | example of this:
           | https://pganalyze.com/blog/postgres-18-async-io.
        
         | eatonphil wrote:
         | Who isn't? Cockroach rewrote Postgres in Go. CedarDB rewrote
         | Postgres in C++.
         | 
         | And then to lesser degrees you've got Yugabyte, AlloyDB, and
         | Aurora DSQL (and certainly more I'm forgetting) that only
         | replace parts of Postgres.
        
       | atombender wrote:
       | This is exciting. The announcement says it will be open source. I
       | really hope that this includes a functionally complete control
       | plane so you realistically self-host.
       | 
       | I looked Neon recently, and it appears that it's designed as a
       | SaaS product from the outset; while it is technically possible to
       | self-host the individual components of the architecture, it does
       | not look trivial, in large part because the control plane is
       | closed source (and probably extremely specific to Neon's SaaS
       | operations).
        
       ___________________________________________________________________
       (page generated 2025-08-11 23:00 UTC)