Amazon Relational Database Service (RDS) vs. RavenDB

Whether your organization is [an] early startup or large company AWS RDS fits in most of the cases such as 1. Easy to start, setup, used by [a] few or large developers team. 2. You can easily scale DB [instances] when your business required scaling as a startup or pay only for [users] to optimize cost as [a] large organization. 3. If your application requires SQL Server, Oracle, or Maria DB then you should use AWS RDS instance. 4. Your application requires better availability and security of data you can use AWS RDS instance. When AWS RDS is not recommended: 1. You need automatic scaling or capacity flexibility as request load gradually increases, better to use Amazon Aurora DB in this case.

Incentivized

If you're a.NET developer searching for a system other than SQL Server for business assessment, then you must try RavenDB. RavenDB is a fantastic document-oriented system that has been specifically developed to work with all.NET or Windows systems. Developers are continually working on such systems to eliminate their flaws while also providing a few benefits. We must refresh ourselves on a regular basis since the free software system is like an open area where anybody may stand up with a brilliant solution to the issue. RavenDB is absolutely worth a look

• Amazon RDS helps organizations handle relational database management tasks such as migration, backup, recovery, and patching. Some of the main features of Amazon RDS are replication, high-performance storage, and failure detection. One of the biggest advantages of Amazon RDS is its ease of use.

Incentivized

• Document Database - no Object-Relational Impedance Mismatch
• ACID support that is optimized for performance
• Can be easily integrated into automated tests (unit tests)
• Easily configurable via C# code
• Comes directly with RavenStudio - no SSMS or SQL Developer required
• In general low footprint when it comes to memory and disk consumption
• Useful safety nets for new developers - e.g. by default an exception is thrown when you make too many requests within a session

• RDS has everything that can be configured, but when you need efficient configuration we need little bit more knowledge about Dev Ops things.
• Although restoration is available, when you need to do it it's pretty tricky. A new instance will be created and you will face some downtime.
• Understanding which configuration and pricing would be suitable for startups as well [as] enterprise needs more reading and research.

Incentivized

• The documentation is very good, but it's sometimes hard to find the topic I'm looking for.
• Updating references is done manually. It would be nice if there was a feature to help with that. I'm not sure that's even possible though.

It has worked reliably in the past, we have not had any problems that would have been caused because of using RDS. Also it's future-proof, it will scale easily if user base of the application that relies on it is going to increase rapidly. Our application deployments also rely on it so renewing it is essential for business & switching to different provider would cause costs without any apparent benefit.

Incentivized

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.

I've been using AWS Relational Database Services in several projects in different environments and from the AWS products, maybe this one together to EC2 are my favourite. They deliver what they promise. Reliable, fast, easy and with a fair price (in comparison to commercial products which have obscure license agreements).

Incentivized

RavenDB is easy to use and provides a very friendly and intuitive management tool. We can now map documents with indexes, transform unstructured data into JSON format and analyze text and spatial data in real-time. With an array of functional features like data visualization, SNMP monitoring, automated data backup, it is seamlessly helping us in managing databases' performance and generating custom reports.

I have only had good experiences in working with AWS support. I will admit that my experience comes from the benefit of having a premium tier of support but even working with free-tier accounts I have not had problems getting help with AWS products when needed. And most often, the docs do a pretty good job of explaining how to operate a service so a quick spin through the docs has been useful in solving problems.

Incentivized

The support is really fast and flexible. Since one single working day, we got a response to our first request, only 4 days later we got a technical demonstration for our complete developer team to get in touch with raven and its performance. Also during our development, we got a quick response to questions.

RavenFS changed along the way and made us change the codes.

[Amazon Relational Database Service (RDS)] is much better to have everything in the cloud instead of having it on-premise once you can get all the benefits from Cloud. Of course, it can be a bit expensive if your company it's not growing anymore but if you check it in detail, you can see that the scalability of Cloud makes a lot of sense and also the reliability.

Incentivized

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.

• Reduced overhead in management of host system
• Reduced maintenance requirements for keeping database engine up to date and applying security patches
• Reduced risk of data-loss during an outage do to automatically configured and maintained multi-zone replication and backups
• Reduced risk of data leakage, leveraging amazon's engineering/admin/ops teams to maintain network and server security.

Incentivized

• 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.