Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

How to use Postgres for everything

github.com

Post reply on HN
Print view View original

11–20 of 181 posts

Re: How to use Postgres for everything

#11

Post by underdeserver »

whateveracct wrote: post #7

Just don't use a single Postgres DB for everything as you scale up to 100+ engineers. You'll inevitably get database-as-the-API. Now if you have the actual technical leadership [1] to scale your systems by drawing logical and physical boundaries so that each unit has its own Postgres? Yeah Postgres for everything is solid. [1] Surprisingly rare I've found. Lots of "successful" CTOs who don't do this hard part.

Drop the scare quotes from "successful". These guys shipped products. The migration to multiple databases, syncing user information etc. is a milestone, not a necessity at every step.

Re: How to use Postgres for everything

#12

Post by CalRobert »

whateveracct wrote: post #7

Just don't use a single Postgres DB for everything as you scale up to 100+ engineers. You'll inevitably get database-as-the-API. Now if you have the actual technical leadership [1] to scale your systems by drawing logical and physical boundaries so that each unit has its own Postgres? Yeah Postgres for everything is solid. [1] Surprisingly rare I've found. Lots of "successful" CTOs who don't do this hard part.

You could go whole hog with postgrest I suppose

Re: How to use Postgres for everything

#13

Post by lokimedes »

Having just spent the better part of two weeks integrating Apache Age for Graph data, just to realize the project is stale and a mess, don’t take this list on face value.

Now hoping for better results with DGraph, but it seems that graph databases are living a precarious existence.

Re: How to use Postgres for everything

#14

Post by jjallen »

CalRobert wrote: post #12
whateveracct wrote: post #7

Just don't use a single Postgres DB for everything as you scale up to 100+ engineers. You'll inevitably get database-as-the-API. Now if you have the actual technical leadership [1] to scale your systems by drawing logical and physical boundaries so that each unit has its own Postgres? Yeah Postgres for everything is solid. [1] Surprisingly rare I've found. Lots of "successful" CTOs who don't do this hard part.

You could go whole hog with postgrest I suppose

I always wonder if postgrest works well after growing quite a bit. I really should google the largest companies using it.

Re: How to use Postgres for everything

#16

Post by jensneuse »

I absolutely love Postgres, but please allow me to say that you absolutely don't want to expose an API generated from a database to people outside of your team. This limits you a lot in changing the way you store your data.

I wrote about this topic before and haven't changed my opinion much. You don't want to have that tight coupling: https://wundergraph.com/blog/six-year-graphql-recap#generate...

Re: How to use Postgres for everything

#17

Post by feverzsj »

jjallen wrote: post #14
CalRobert wrote: post #12

Earlier quoted context omitted.

You could go whole hog with postgrest I suppose

I always wonder if postgrest works well after growing quite a bit. I really should google the largest companies using it.

In my experience, without careful tunning, postgres performance starts dropping significantly around 10 million rows.

Re: How to use Postgres for everything

#18

Post by dunwaldo »

jensneuse wrote: post #16

I absolutely love Postgres, but please allow me to say that you absolutely don't want to expose an API generated from a database to people outside of your team. This limits you a lot in changing the way you store your data. I wrote about this topic before and haven't changed my opinion much. You don't want to have that tight coupling: https://wundergraph.com/blog/six-year-graphql-recap#generate...

you could use views as a layer in between?

Re: How to use Postgres for everything

#19

Post by anonzzzies »

whateveracct wrote: post #7

Just don't use a single Postgres DB for everything as you scale up to 100+ engineers. You'll inevitably get database-as-the-API. Now if you have the actual technical leadership [1] to scale your systems by drawing logical and physical boundaries so that each unit has its own Postgres? Yeah Postgres for everything is solid. [1] Surprisingly rare I've found. Lots of "successful" CTOs who don't do this hard part.

You don't have to plan this very early; most companies won't get to 100+ engineers. Let's ship first and worry about this, much much much much later. Overarchitecting stuff makes life hard; coming into companies that have 40 servers running with everything architected for 1000000 engineers and billions of visitors while in reality there aren't even 2 users and there is 1 overworked engineer. Stop doing that and stop people telling to do that.
Post reply on HN