Neki – sharded Postgres by the team behind Vitess

122 points | by thdxr 5 hours ago

4 comments

• atombender

  1 hour ago
  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).
• shoeb00m

  4 hours ago
  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

  [-]
  • dangoodmanUT

    48 minutes ago
    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
  • n2d4

    3 hours ago
    There is also pgdog by the author of pgcat: https://pgdog.dev
  • qaq

    3 hours ago
    Supabase also working on OrioleDB
    [-]
    • eatonphil

      3 hours ago
      OrioleDB is not about sharding, it's about the storage layer.
      [-]
      • qaq

        2 hours ago
        I did not claim OrioleDB is about sharding. It was just an observation that Supabase is contributing to Postgres ecosystem through multiple projects.
        [-]
        • selfhosttoday

          2 hours ago
          they likely said that because the context is "vitess for postgres projects" and OrioleDB is not "vitess for postgres"
• hubertzhang

  2 hours ago
  Does Neki still need sharding key in query, just like Citus?
• ozgrakkurt

  1 hour ago
  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

    1 hour ago
    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

      1 hour ago
      The Postgres team incorporating io_uring into PG 18 is a good example of this: https://pganalyze.com/blog/postgres-18-async-io.
  • eatonphil

    1 hour ago
    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.