Lead Core Reliability for Clickhouse https://github.com/clickhouse/clickhouse, previously CTO at Tembo, EM at Microsoft & Head of Solutions Engineering at Citus Data
I don’t know if this is a question for you or for the Supabase leadership team. But, what is the primary reason for building something “new” instead of using the tools already existing in the Postgres ecosystem like Citus or pgdog?
What are the gaps in those which you expect to solve with Vitess for Postgres?
Also, several Postgres providers now also provide a SQL editor / runner and table visualizer in their UI.
What do Postgres users here think is the biggest missing thing in current clients? Are they too heavyweight? Too generic and don't support advanced Postgres features? Don't look modern enough? Not mobile friendly? Or is it something else?
It's much newer for one, so it's behind on features. But, we're working on adding new ones based on customer demand.
We want to build it with a PostgreSQL license using existing community extensions as much as possible and build custom stuff (still permissively licensed) only when necessary.
Introducing Skyryse One – the world’s first production aircraft operated by a single control stick, two touchscreen displays, and powered by SkyOS.
SkyOS is our proprietary fly-by-wire and flight control system, offering a level of control and safety never seen before in general aviation. More than autopilot, SkyOS provides true full flight management, seamlessly integrating with the most intuitive flight controls ever designed.
Paper has a theory for the observation that older siblings earn more than younger ones.
TL;DR: Older siblings come home, get their younger siblings sick, negatively impact their development at a critical age and, as a result, make their adult labor market outcomes worse.
Stacks[1] are basically recipes for deploying Postgres for specific use cases. This includes extensions, Postgres configs and application deployments (example: PostgREST)
We're proud to announce the general availability (GA) of Tembo Cloud, a managed Postgres service that unlocks the full power of the Postgres ecosystem.
Tembo Cloud currently provides 194 Postgres extensions and 9 Tembo Stacks that make it easier to use Postgres for non-typical workloads such as vector search, ML, data warehousing, message queue, geospatial and more.
Agreed. Putting data for all your use cases in a single database is a huge deal. Having different databases for each part of the application bloats so much so easily from a cost, complexity and skill set standpoint. Also, makes it extremely hard to debug issues when you have to chart the path of data through 5 different tools.
There is the challenge of workload separation and scaling each component separately but that can be resolved by pulling out challenging workloads into their own "database" albeit on the same stack.
Fair feedback. We only have a free tier until now. We're rolling out pricing and billing in the upcoming days and will launch a pricing page soon after to be explicit.
I don't have the data for the average age, but I was recently in a conversation around how long does it take to become a committer since getting involved in Postgres by writing code for it.
So, I wrote a couple git commands like below [1] to figure out when someone was first named in a commit message vs when they made their first commit (as a committer) for the last 10 people who became committers.
The average time of involvement was ~8.9 years (just comparing month / year), with the lowest being ~6.5 years.
Obviously one could do better analysis but my goal was just to get an approximate understanding.