We performed a comparison between Cassandra and PostgreSQL based on real PeerSpot user reviews.
Find out in this report how the two Vector Databases solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."The most valuable features are the counter features and the NoSQL schema. It also has good scalability. You can scale Cassandra to any finite level."
"The technical evaluation is very good."
"A consistent solution."
"The time series data was one of the best features along with auto publishing."
"The most valuable features of Cassandra are the NoSQL database, high performance, and zero-copy streaming."
"Some of the valued features of this solution are it has good performance and failover."
"We can add almost one million columns to the solution."
"The use of Cassandra in real-time data analytics has been pivotal for our e-commerce platform. As our platform operates 24/7, providing services to sellers and customers alike, the need for real-time updates is paramount."
"It's a transactional database, so we use Postgres for most of our reporting. That's where it's helping."
"The solution has many valuable features such as it easy to use and the interface is intuitive."
"We often use PostgreSQL for operations monitoring because we are a manufacturing company."
"What I like is that it's quite powerful in terms of performance."
"It's quite scalable."
"Postgres has some functions called JSONB aggregators or other aggregators, which are quite useful."
"It's a useful solution, that can be widely used."
"The product is very similar to the SQL Server."
"The secondary index in Cassandra was a bit problematic and could be improved."
"The solution doesn't have joins between tables so you need other tools for that."
"It can be difficult to analyze what's going on inside of the database relative to other databases. It can also be difficult to troubleshoot sometimes."
"Interface is not user friendly."
"Doesn't support a solution that can give aggregation."
"The initial setup of Cassandra can be difficult in the configuration. There might be a need to have assistance. The implementation process can six months for connecting to certain databases."
"Cassandra can improve by adding more built-in tools. For example, if you want to do some maintenance activities in the cluster, we have to depend on third-party tools. Having these tools build-in would be e benefit."
"Depending upon our schema, we can't make ORDER BY or GROUP BY clauses in the product."
"PostgreSQL could improve by providing a geographical solution for tracking trucks and people in the field. They might already have features similar to this and I have not found them. I haven't done research about this topic."
"PostgreSQL doesn't have a feature for temporal SQL, which is useful for gathering versions of data. This feature should be included in PostgreSQL. This feature is available in MariaDB, SQL Server, Oracle Database, and DB2."
"They need to have a better graphical interface. There is a tool called pgAdmin 4 that they use, which is free. It is written in Java, and it is slow. They need to have a better product that is similar to Toad for Oracle, but, of course, it is hard to get something that's really great and free. Other than that, it is great."
"If it was free to use, it would be the perfect solution."
"Instead of the installation agent downloading all the packages for the install, it should allow the user to download the packages separately on their own to do the install."
"It still needs to be more mature and have some backup feature. We are normally dealing with Oracle's data, and we have very strong online tools to back up the data and do other things. PostgreSQL still needs to do more in this area as well as in the high availability area. There are many external tools that you can use for PostgreSQL's high availability, but there is no embedded tool within PostgreSQL for high availability. It could have a feature similar to Oracle for working on a distributed system. It can have some scripts to improve the monitoring and some tools to do performance analysis. We have a workaround for most of such requirements except for the support for a distributed system, which is very difficult to have. This area should be included in the core of the database itself."
"PostgreSQL uses high memory compared to its counterparts when a highly demanding load is involved, especially one that makes many concurrent connections to the database."
"It is possible that in the newer version this has been addressed, but I would like the deployment in microservices architecture could be improved."
Cassandra is ranked 11th in Vector Databases with 19 reviews while PostgreSQL is ranked 7th in Vector Databases with 123 reviews. Cassandra is rated 8.0, while PostgreSQL is rated 8.4. The top reviewer of Cassandra writes "Well-equipped to handle a massive influx of data and billions of requests". On the other hand, the top reviewer of PostgreSQL writes " Real-time data capture optimizes database performance but Views create problems". Cassandra is most compared with Couchbase, MongoDB, InfluxDB, ScyllaDB and Oracle NoSQL, whereas PostgreSQL is most compared with Firebird SQL, EDB Postgres Advanced Server, MySQL, MariaDB and SQLite. See our Cassandra vs. PostgreSQL report.
See our list of best Vector Databases vendors.
We monitor all Vector Databases reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
