How to use Postgres for everything
github.com
How to use Postgres for everything
1–10 of 181 posts
Re: How to use Postgres for everything
#2I like this.
I strongly believe that picking some tech stack you know when you are starting out is always the right decision, until it's not. Only then do you pick a different solution.
Better to move fast leveraging what you know, until you need something else.
Re: How to use Postgres for everything
#3If anyone has seen a steams implementation in Postgres please let me know. Not just pub/sub, but full implementation of streams with consumer groups would be very interesting to me.
Second best, how would you implement this in Postgres? I’m tempted to give it a go but I haven’t a fully-baked plan yet.
Re: How to use Postgres for everything
#4[flagged]
Re: How to use Postgres for everything
#5"It's inspired by this article from the Amazing CTO [0]"
Getting up in the morning, seeing an article that references you, bliss!
Re: How to use Postgres for everything
#6Broken markdown.
- the entire repository is 1 file
- the file is titled "read me"
- but you didn't read it (it's not proofread)
why do you want me to read something you did not read?
Re: How to use Postgres for everything
#7Just 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.
Re: How to use Postgres for everything
#8Postgres administration is such a PITA. I'd rather use sqlite for everything.
Re: How to use Postgres for everything
#9Just 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'll inevitably get database-as-the-API
I think that's actually the point of "postgres for everything"?
Re: How to use Postgres for everything
#10Just 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'll inevitably get database-as-the-API I think that's actually the point of "postgres for everything"?
If you don't have any discipline it becomes hell.
Not to mention that a random team writing a migration that locks a key shared table (or otherwise chokes resources) now causes outages for everyone.