@fallenhitokiri@social.screamingatmyscreen.com

Post #2445496

2023-09-22 06:17 UTC

@chrisg@fosstodon.org it’s part of it, I think the other points are - it scales nicely vertically and horizontally, something we don’t often see - there aren’t many use cases where anything else outperforms a SQL database - there are nearly none (except very specific use cases and scale) where a SQL DB doesn’t perform And some of the special cases are covered by extensions such as PGvector and postGIS. (Unrelated - Hugos standard RSS location is hard to guess on mobile, needed my desktop to inspect source)

Replies (2)

@chrisg@fosstodon.org 2023-09-22 06:51

@fallenhitokiri@social.screamingatmyscreen.com For simple schemas I agree, tables work fine. But if, for example, you want fast traversals on thousands of joins, a graph dbms wins. If you want simplicity of design, docs are the way to go. To me, "performance" is not just ms/query. It's also about $/query. Ease of use. Tunability/adaptability. Schema extensibility. Federation. I am sure you can tell me of RDBMSs that have these. No doubt. The question I have is can we make a new _model_ that supports these things.

Open ##2445497
@chrisg@fosstodon.org 2023-09-22 06:51

@fallenhitokiri@social.screamingatmyscreen.com > Unrelated - Hugos standard RSS location is hard to guess on mobile, needed my desktop to inspect source Thank you for this, I didn't know. What is the expected location?

Open ##2445498