Every query in Neki gets two plans.
The Neki plan decides which shards run the query and how their results are combined. Postgres then decides how each shard executes its work.
A closer look at the Neki router:
At some point, throwing more CPU and RAM at your Postgres instance won't solve your scaling problems.
What comes next is sharding.
It used to be a huge pain. Neki changes this.
You've just been paged. Every database query is failing to execute. Figure out why.
This exact question is how early GitHub hired its DBAs.
The answer in our latest blog: planetscale.com/blog/debugging…
Join us on September 10th for a first look at Neki, our sharded Postgres product. We’ll have talks from our database professor @BenjDicken, CTO @NickVanWig, and some members of the @getneki team doing a deep dive into Neki’s architecture.
