PostgreSQL (alternately Postgres) is a free and open source object-relational database system boasting over 30 years of active development, reliability, feature robustness, and performance. It supports SQL and is designed to support various workloads flexibly.
N/A
RavenDB
Score 8.1 out of 10
N/A
RavenDB is a NoSQL Document Database that is fully transactional (ACID) across the database and throughout clusters. The database minimizes the need for third party addons, tools, or support to boost developer productivity and get projects into production fast. Users can setup and secure a data cluster deploy in the cloud, on-premise or in a hybrid environment. RavenDB offers a Database as a Service solution, allowing users to pass on all…
First It's open source and it's cost-effective compared to other databases.PostgreSQL can be easily integrated with numerous platforms. It is well known and appreciated so relying on it as our system database can be easily accepted by our customers. And if your developing a …
For our use cases, PostgreSQL is just as feature rich as other options, costs less, and is simple to get up and running. There is also a plethora of documentation to support it which makes it a great option for a small scale startup without needing high levels of expertise to …
In this case, Postgres is preferred because it handles large data sets and requires fewer hardware resources than its competitor, MySQL. Compared to PostgreSQL, Microsoft products are excellent, but the installation process for MS SQL is lengthy. PostgreSQL has an advantage …
I've been using different databases for the past 20 years, solutions like MS SQL Server, MySQL, MariaDB, Interbase, Firebird, DB2, etc., and by using them I wasn't able to be neither close to the performance PostgreSQL deliver. Also, it is one of the most popular databases on …
Although the competition between the different databases is increasingly aggressive in the sense that they provide many improvements, new functionalities, compatibility with complementary components or environments, in some cases it requires that it be followed within the same …
We evaluated both PostgreSQL and MySQL, two popular open source relational databases. While they are very similar in most areas, PostgreSQL's reliability and performance won us over, plus it has much better support from cloud vendors we also work with.
Postgres stacks up just [fine] along the other big players in the RDBMS world. It's very popular for a reason. It's very close to mySQL in terms of cost and features - I'd pick either solution and be just as happy. Compared to Oracle it is a MUCH cheaper solution that is just …
A free corporate professional product. Who does not want to have such a thing, we hesitated because we did not know the product before and frankly we did not want it at first. But when we give it a chance, it has been running smoothly for years.
When we were originally evaluating Redshift we ran into some issue with dates. Either way, Postgres is a better choice than Redshift because it avoids vendor lockin. We ended up choosing Postgres over MySQL because it was easier at the time to get a hosted Postgres cluster up …
As I have been telling all along, PostgreSQL is much cheaper compared to the other RDBMS solutions. It has got better performance with some of the application services that we are using and is easy to maintain. Overall, we are satisfied migrating to PostgreSQL database clusters.
Much more mature and stable when compared to MySQL with features such as MVCC, complex subquery plans, ORDBMS, and NoSQL support. With Oracle retaining rights to MySQL its future as an open database is less secure and is no longer in the hands of the community. PostgreSQL also …
Its main characteristic is the integrity of the data. In addition, being free software, it has no costs associated with its license, which allows the number of installations to be scaled without problems.
The technical staff quickly learns about its installation, configuration …
Both Oracle and MS-SQL database option fell when we evaluated the effect on our overall solution cost to our customers. customer examine the overall cost of the solution they buy, selecting Oracle or MS-SQL would leave less money in our pockets. We are Linux based solutions and …
PostgrPostgreSQL as a transaction db engine against oracle and sql server works well. TPM wise compared to MySQL and MariaDB, on an evan scale. SQL function supports, far outweighs compared to MySQL and MariaDB. PG Extensions allow for flexibiltity and scalability. Allows …
We selected PostgreSQL due to the number of employees who have used it in the past. The data consistency guarantees. The multiple transaction isolation levels support.
PostgreSQL outperforms every other option. It is faster, more flexible, more reliable, easier to maintain, and more consistent in behaviour than any of the other offerings.
The main reason for select PostgreSQL against MS SQL Server Express edition is the necessity to use open-source platform, without any issues for licensing, client licensing, etc. etc, which is usually follows developers and project managers when they start to use products and …
SQL Server is an excellent product from Microsoft, it is a derivative from Sybase which originally developed the SQL Server form Unix and Linux, and Microsoft purchased it to migrate the DBMS to Windows Server. But the cycle comes full circle, and now Microsoft recommends its …
It's a viable alternative, with a rich feature set and a reliable system. PostgreSQL is one of the best RDBMS's currently on the market in 2020, it serves just as well as a starter, PoC DB for any software idea as a final, highly valuable database solution for big systems.
MySQL: As I mentioned before, MySQL has superior write performance. However, Postgres has super read performance and safer ACID transactions, i.e. less potential data loss. Elasticsearch: we use Elasticsearch to store free-form customer data, but that's a different use-case. …
PostgreSQL is rich in features and free to use which is perfect for our organization. PostgreSQL is our goto RDBMS if we want to create an application or services backend with the database if there's no specific requirement. For example for the most important and largest …
PostgreSQL beats every other RDBMS offering for being truly Open Source. Since it does not belong to a specific company it is poised to remain as such for a long time to come. PostgreSQL has a huge user base and active community. The releases are coming out often with …
First of all, Microsoft Access is also a powerful, efficient, and free database. But the feel of it, I mean the GUI is not all great for me. It is very eye-stressing. MongoDB is also a good database, it too is efficient, productive, and powerful. But, upon this, RavenDB is a …
The team is very nice, very helpful, and answer very fast to any answer you may have. Thanks to their help, we were able to use and understand all the RavenDB features in no time! Documentation for server and client is very clear, with a lot of use cases. Maintenance is easy, …
RavenDB is just smarter than the competitors. The mapping reduction sorting is head and shoulders above everything else I've used. Nothing really approaches comparable in terms of complexity. Because of the searching of predetermined categories, read efficiency is terrible. …
The company needed a cache server that was closest and the most accessible, which is why we are currently experimenting with RavenDB which gives us the option to set up our hub in a local setting.
Much better support, more transparent pricing, much more easy setup process, native integration into c# / net core. We also tried to set up a Mongo Atlas cluster by self-study but weren't able to get this running. There is a much better response when searching in google, but a …
While MongoDB is in general more popular, I cannot fathom why that is. If you want ACID support (and as a developer, you'll always want that), MongoDB is way slower when compared to RavenDB. Furthermore, RavenStudio is just integrated, while
[RavenDB is] just simply much cleverer than the competition. The map reduce indexing is a league above anything else I have used. Nothing else comes close on abstraction as well. Read performance is terrifying due to querying pre calculated indexes. It is just a pity it is not …
Having ACID compliance is a big enough reason to choose RavenDB over the other products. You don't have to worry about losing your data if the plug is pulled. You're able to perform many actions within a transaction and not worry about your data being in a bad state if the …
Installing and configuring. We had some big issues with indexing the data after the documents were created and wanted to expand the index, with millions of records this task mostly did not complete despite a dedicated server.
Out of the many variants of document and SQL databases out there that we have used, RavenDB is our no 1 choice for anything but the smallest projects which can be served with a very small SQL instance. Other than that, RavenDB packs more features and is easier to work with than …
The given alternatives are also powerful and really good noSQL databases but the highest availability of RavenDB allows me/us to know it a lot better. RavenDB is encrypted by default wherever we use it in production and it has a high level of documents compression.
As I have said before in the previous questions ... RavenDB has a very simple clean UI, but stacks up in its power. Though new to me, I have found it to be much easier to learn and use than my previous database - Microsoft SQL Server. RavenDB's simple design and meaningful …
Being that ACID and cluster transaction support is a big plus against all of them. Cool prices on Azure and AWS is another plus. The ability to search between millions of documents.
When I first started using RavenDB, I did evaluate Mongo DB but found it to be lacking. The primary issue was that Mongo DB did not support atomic consistency for the persistence of multiple documents at the same time, although I think this may not be an issue with subsequent …
Once I had got my head around the concept of a document database it was a happy bye-bye to SQL Server. Firebird - far too fiddly - I found myself writing a silly API to sit on top of Firebird just to do the most basic things. MongoDb - in the very short time I spent with it, it …
We chose Raven over Mongo because it has robust support for multi-document transactions, first-class .NET and LINQ support, a well-designed API that has inspired imitation and has better tooling out of the box. We chose Raven over Redis because Raven is a full persistent …
PostgreSQL is ideal for handling databases that contain large volumes of information due to its efficiency, speed and above all because of the good management it makes of our resources, it also behaves very well in distributed environments of high demand, if you want a database of stable data and excellent performance PostgreSQL is one of the best.
RavenDB is very well suited for NoSQL beginners to start easily setting up and using a NoSQL database. Also to set up a high performance and high availability cluster is possible without reading tons of documentation. Very straightforward assistant! The performance is really high.
The performance of PostgreSQL has been enhanced through the years, but always is better to have as much performance as we can.
The replication services could be done directly within the database, and more easily.
The Object Orientation of the Database could be extended, and albeit it manages inheritance of tables, and accepts XML and JSON as primary types, it would be wonderful if one could attach methods more easily to tables (to make them more like classes), and instances (rows for example).
We've had an excellent experience using RavenDB. Internally we are testing the newer features in 5.0 such as time series, which will effect the con specified previously dependent on the real world performance. We foresee that BattleCrate will continue to use RavenDB as we grow.
Postgresql is the best tool out there for relational data so I have to give it a high rating when it comes to analytics, data availability and consistency, so on and so forth. SQL is also a relatively consistent language so when it comes to building new tables and loading data in from the OLTP database, there are enough tools where we can perform ETL on a scalable basis.
Really good .NET client that is very easy to use. The management studio is excellent and puts anything that Microsoft or Oracle have to shame. Very quick to develop with once the complexity hurdle has been overcome. Initially using it can be a bit painful until you fully grasp the event sourced nature of the indexing.
The data queries are relatively quick for a small to medium sized table. With complex joins, and a wide and deep table however, the performance of the query has room for improvement.
AWS, Heroku, and Digital Ocean all provide Postgres-as-a-service, where you pretty much never need to administrate it yourself but they do it for you. The Postgres community also has developed awesome and reasonably priced extensions, such as Citus DB and CockroachDB in case you need additional support for running it. If you need documentation, Postgres's docs are super thorough and their official forms are active.
Had a question that was answered in minutes. Never used a NoSQL approach before, but was able to be proficient in a matter of hours. Easy to read API Documentation. 5 out 5 support in book, I have never once ran into an issue that wasn't quickly solved by either their support team or myself doing a quick search online.
The online training is request based. Had there been recorded videos available online for potential users to benefit from, I could have rated it higher. The online documentation however is very helpful. The online documentation PDF is downloadable and allows users to pace their own learning. With examples and code snippets, the documentation is great starting point.
In this case, Postgres is preferred because it handles large data sets and requires fewer hardware resources than its competitor, MySQL. Compared to PostgreSQL, Microsoft products are excellent, but the installation process for MS SQL is lengthy. PostgreSQL has an advantage over its competitors in that it can adapt or configure third-party programs, applications, or settings.
RavenDB is just smarter than the competitors. The mapping reduction sorting is head and shoulders above everything else I've used. Nothing really approaches comparable in terms of complexity. Because of the searching of predetermined categories, read efficiency is terrible. RavenDB is a storage system designed for the current websites and functional prototypes. It has an easy-to-use interface and enables quick replication and backup installation. Furthermore, technical assistance responds quickly and walks you through the implementation and deployment procedures.
Easy to administer so our DevOps team has only ever used minimal time to setup, tune, and maintain.
Easy to interface with so our Engineering team has only ever used minimal time to query or modify the database. Getting the data is straightforward, what we do with it is the bigger concern.
RavenDB has saved my customers a lot of money with their cloud services' tiered model. The database is able to grow with the project/company and can start out small at a low cost.
RavenDB is free for three nodes and three CPUs, which makes it great for development scenarios. You're able to start rapidly building applications without having to worry about licensing.
Scaling out has allowed us to use three small cloud servers when starting out and get the performance and throughput of a single larger server.