In your comment you tell they preferred maintain Postgres over a NoSQL database. I think SQL and NoSQL database have different scopes. While SQL are the best option for structured data (like I think is the case of Lemmy), NoSQL databases are better for unstructured data. So the best option depends of the context. About the SQL database performance, today different solutions and options exist to deal with this problem despite the amount of data managed: from in memory databases to a rack of front servers working against a RAID cabin of SSD disks, the capability of make table splits by some field like year to speed up the response time, etc
this post was submitted on 10 Jun 2023
9 points (100.0% liked)
General Programming Discussion
7740 readers
2 users here now
A general programming discussion community.
Rules:
- Be civil.
- Please start discussions that spark conversation
Other communities
Systems
Functional Programming
Also related
founded 5 years ago
MODERATORS
Do you mind sharing a link to that article? Sounds interesting!
I think a lot of this has to do with your table design and general query efficiency. Choosing the wrong structure early on will force you to migrate earlier. If you're really thoughtful and intentional with your DB design, I can definitely see a single Postgres instance scaling to handle the vast, vast majority of web applications.
The article link is the post :)
Ah! Apologies - still learning the ropes with Lemmy 😅
Yeah databases scale well in my experience, with good indexing and all it can all be handled reasonably well. Also managed serverless scaling is offered by AWS so that's always cool.
view more: next ›