Unlike PostgreSQL, ScyllaDB is not as general-purpose and covers fewer use cases due to its query limitations. It doesn’t have the luxury of rich query capabilities found in PostgreSQL, such as joins, aggregates, subqueries, geospatial queries, and more. Additionally, ScyllaDB does not fully support ACID properties, making it less ideal in terms of consistency and data integrity

This is the most important part of the article imo

I ran into the same issue a few weeks ago. In my case I didn't need real-time updates but I still needed to bulk insert data, which Postgres is terrible at (especially when dealing with tens of millions of rows). I just ended up using MariaDB (since that was my first exposure to SQL and I don't remember having issues with it) and turns out it can handle bulk inserts a lot better without slowing down much. I wish PostgreSQL was better.