[flagged]
If you’re going to make a ragebait comment you should ideally provide some kind of basis beyond “waaaah everybody except me is stupid”
How to use Postgres for everything
51–60 of 181 posts
Re: How to use Postgres for everything
#52If 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.
Have a look at diogob/postgres-websockets or supabase/realtime.
Re: How to use Postgres for everything
#53Thanks for the gist mention!: https://gist.github.com/cpursley/c8fb81fe8a7e5df038158bdfe0f...
Re: How to use Postgres for everything
#54Re: How to use Postgres for everything
#55Wonder if someone can write a SQLite for everything article too - would be far more difficult though if considering HA.
Re: How to use Postgres for everything
#56Being stuck with MariaDB/MySQL in some projects, I recently compared it to PostgreSQL and found many of these extended capabilities existing there also, including JSON, temporal tables (w/ SYSTEM VERSIONING), columnar and vector storages etc.
LISTEN/NOTIFY type functionality was sort of missing but otherwise it was surprising how it is keeping up also, while little of that is probably being used by many legacy apps.
Re: How to use Postgres for everything
#57Just 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.
Unfortunately a lot of places teach software engineers to build over complexity before they need it. I like to remind people that StackOverflow ran on a couple of IIS servers and a msSQL db for a good while before scaling up to a little more than a couple of IIS servers. Hell they didn’t even do the CDN thing until 2017 or something similarity “crazy”. Mean while you have hordes of developers who write interfaces which will only ever be consumed by a single class because they’ve been taught to do so.
As I see it the only way to look at scaling issues is that you’ve made it. Almost no user facing software will ever reach a point where something like Django couldn’t run it perfectly fine. It’s when you do, you build solutions, which sometimes means forking and beating the hell out of Django (Instagram), sometimes going into Java or whatever, spreading out to multiple data bases and so on. Of course once you actually hit the scaling issues you’ll also have enough engineers to actually do it.
Re: How to use Postgres for everything
#58Earlier quoted context omitted.
What do you mean local first? Postgres is an executable that you can run on your machine if you wish
I mean storing data in your https://localfirstweb.dev . Sqlite allows that so you can work fully in our client (browser/mobile) without internet potentially and then later sync (rqlite, pouchdb, etc for instance). If I get to do 'everything' with postgres, I need that too, so I was wondering if it exists.
https://electric-sql.com/ does this, running a stripped-down version of postgres on the client.
https://www.powersync.com/ is a similar approach, but using sqlite on the client.
https://zero.rocicorp.dev/ also deserves a mention, but I believe it’s more of a read cache with writes going directly to the server. I’m not sure if it supports SQL client-side or has its own ORM.
Re: How to use Postgres for everything
#59"It's inspired by this article from the Amazing CTO [0]" Getting up in the morning, seeing an article that references you, bliss! [0]: https://www.amazingcto.com/postgres-for-everything/
> Use Postgres for Fulltext Search instead of Elastic
pg fulltext search is very limited and user unfriendly, not a great suggestion here
Re: How to use Postgres for everything
#60While we are it - are there any good resources on how to best self host a Postgres database? Any tips and tricks, best practices, docker / no docker etc? I’m looking to self host a database server for my multiple pet projects, but I would love to get backups, optimizations and other stuff done well.