Amazon RDS Reviews

Amazon RDS is primarily for web applications.

The solution is good for on-premise deployments.

The solution could improve by adding a sandbox environment and more security.

I have been using Amazon RDS for approximately one year.

I rate the stability of Amazon RDS a five out of ten.

I plan to increase the usage of this solution.

I rate the scalability of Amazon RDS a five out of ten.

I rate the stability of Amazon RDS a nine out of ten.

Positive

The setup of Amazon RDS was complex.

I have received a return on investment using the solution.

The price of Amazon RDS is reasonable.

I rate Amazon RDS a ten out of ten.

We have a lot of benefits moving to managed services, including Amazon RDS. It is a great service, and we have a lot of cases needing Amazon RDS. So, it is a great product.

We have some cases where our customers are looking for more performance or simplifying their DR. So, in this way, we have some cases where the customers moved from EC2 using enterprise license to Amazon RDS with less cost or with included standardization. So, we have cases of moving from EC2 to RDS to simplify the management and also simplify the DR strategy.

The most valuable feature is how simple it is to implement the solution's multiple phases, and also and also have the DR strategy on Amazon. For me, I think it is a great feature how simple it is to increase the performance of instances running on Amazon RDS.

For me, I think that it will be great to have the option to have more SQL or have a deployment allowing for configuring it with a Microsoft SQL server.

Currently, speaking of Microsoft SQL on RDS, you don't have a full option to be able to use it directly on RDS. So, it needs improvement. It will be good to have more solutions with a simple deployment. So being in one region, you should have the option to deploy the solution in another region.

I have been using Amazon RDS for three years. Also, I am using the solution's latest version.

Stability-wise, I rate the solution a nine out of ten.

Scalability-wise, I rate the solution a nine out of ten.

I haven't used the support, but as a partner, I rate the support a ten out of ten since we have a lot of technicians, like solution architects and so on. So the support is great. And we also have feedback from the customers regarding the tech support manager and the support they received. So, overall it is great.

Positive

The initial deployment of RDS was straightforward since our teams have experience.

I have seen a return on investment using the solution.

The pricing of RDS is a little bit high compared to Microsoft. But we know that it is related to Microsoft licenses. However, it is a good price compared to other solutions.

I would recommend the solution to others. I rate the overall solution a ten out of ten.

Amazon RDS helps with information regarding the customer's business performance.

The solution has helped us have valuable metrics on our customer's business.

The most valuable feature of Amazon RDS is its performance.

The solution could improve the administration tools.

I have been using Amazon RDS for approximately three years.

The stability of Amazon RDS is good.

We do not have plans to increase the usage of the solution.

I have not used the support from the vendor.

The initial setup was straightforward.

We have seen an ROI using the solution.

Amazon RDS is less expensive than other solutions.

I rate Amazon RDS a nine out of ten.

We primarily use the solution for internal systems and the database.

The performance has been fine. We have no complaints in regard to the speed.

It is very easy to set up initially.

It is stable and reliable.

I do not have complaints about RDS.

The solution tends to have a lot of updates. It's a very short time before we need to update again.

Technical support could be better.

They should make it cheaper for the users. 

I've been using the solution for ten years. I've used it for quite a long time. It's been a decade or so. 

The solution is very stable and reliable. There are no bugs or glitches. It doesn't crash or freeze. It doesn't break down.

The support is not so good. We did choose the support level that was a little cheaper, and we don't find them to be that helpful or responsive. 

The setup process is simple and straightforward. It is not overly complex. 

It only takes about ten to 20 minutes to deploy the product. It's very fast.

I have found the price to be a little bit too expensive. 

We're an Amazon partner.

I'm not sure which version of the solution I am using. 

I'd rate the solution nine out of ten.

Amazon RDS is custom development. 

Some databases that we would like to use are lightweight and simple to integrate with the application.

Amazon RDS is lightweight and flexible.

It's a secure solution.

The security features could be improved.

I have been working with Amazon RDS for three years.

It is part of the cloud migration solution.

Amazon RDS is quite stable.

Amazon RDS is a scalable solution.

RDS is a single instance. However, the actual users are approximately 500 people, both direct and indirect.

We have stopped using it.

I have not contacted technical support.

In the past, I used Amazon SimpleDB, Amazon EMR, and Amazon Redshift, but I no longer use them.

The initial setup is satisfactory.

It took two weeks to complete the installation.

We have three engineers, one lead, and one manager to maintain this solution.

With the help of our in-house staff, we completed the installation on our own.

Licensing fees are paid on an annual basis.

I would rate Amazon RDS a ten out of ten because it is lightweight, and the flexibility.

Amazon RDS is used for SQL Databases.

The most valuable aspect of Amazon RDS is it is on the cloud.

Amazon RDS could improve by having more sophisticated. I use other solutions that have better technology for more difficult tasks.

I have been using Amazon RDS for approximately two years.

The version of Amazon RDS depends on the database being used.

The stability of the solution depends on the RDS being used. For example, Aurora is not stable but Postgres is. The stability could improve.

I rate the scalability of Amazon RDS a six out of ten.

The level or quality of support depends on how much you are paying for support. If you are paying for premium support then it will be better than the standard support offering.

The initial setup of Amazon RDS is simple. The deployment is quick because of automation. It can be done in less than 10 minutes.

The solution does not require human intervention for deployment. You can simply load it into the pipeline and the pipeline will deploy it automatically.

I rate the initial setup of Amazon RDS a ten out of ten.

Amazon RDS could improve by reducing the price.

I rate the price of Amazon RDS an eight out of ten.

We have a few engineers doing the maintenance of the solution. They maintain the standardized code that everyone uses.

My advice to others is for them to use a different solution, such as Aurora, DynamoDB, or MongoDB. Amazon RDS is only used if the user wants to use a legacy-type application.

This is a well-established solution.

I rate Amazon RDS a seven out of ten.

The primary use case is when you have to host your application on the Amazon cloud and your application uses database. Amazon RDS supports the following database engines: Amazon Aurora, PostgreSQL, MySQL, MariaDB, Oracle Database, and SQL Server database. Amazon provides AWS Database Migration Service to migrate your existing databases to the Amazon cloud. It automates many aspects of database management viz hardware provisioning, database set up, database patching, and backups, which frees your database administrator to focus on important tasks. It also saves on the DB licencing costs.

It makes it easy to administer the database. It helps to scale your database by providing Read Replicas, which reduce transaction time. It is highly available and durable which helps in disaster recovery and management. 

It is also secure. You can build your own VPC and host the database inside it, which will produce robust security. You still need to follow the principles of security as highlighted by Amazon. 

Most useful is its availability to support multiple databases, such as Aurora, MySQL, Oracle, SQL Server, MariaDB, and PostgresSQL. Your application can use multiple databases as required. Combine that with the Automated CI/CD tools, this makes it easy to implement the microservices architecture, which is the need of the hour for web based applications. The capability provided by the RDS to automate a portion of the RDBMS tasks, such as backups and performance tunings for multiple database engines, helps to save on DBA time and cost.

The Amazon RDS engine could provide features for additional databases, such as Db2. It could also provide support for other databases, such as NoSQL databases, DynamoDB, and Apache Cassandra. They could all stay under one hood.

Another improvement that Amazon could do is to market their product so that more customers can use it. With Microsoft having its own cloud Azure hosting SQL Server databases and Oracle coming up with its own cloud, there appears to be more competition. As more customers move to Amazon cloud, it will increase the utilization of the RDS, then more customers will be able to harness the power of Amazon Relational Database Service (RDS).

I have been using this solution since 2015 on my consulting projects with a variety of clients.

This Solution is very stable, as many customers have witnessed. Responsibility to set up the Amazon VPC, servers, and RDS does take work. This requires a solid AWS (infrastructure): Administrators and networking team. They need to work with the AWS team, following the stringent security guidelines that will help to build stability for the solution. 

Amazon Web Services is built for scalability. RDS is designed with scalability in mind.

It is available. You need to negotiate and engage their services.

Earlier, we were using traditional on-prem databases. The need to switch to Amazon RDS has been due to a variety of factors. One such factor is the need to move the existing applications in our data center with variable demand utilization and pre-installed servers and databases to applications migrated to Amazon Web Services cloud. Along with migrating applications on servers, we also need to migrate databases. With the added power of supporting multiple database engines as well as automating many functions of DBAs and releasing the DBAs to focus on essential tasks, this has made it easier to switch to Amazon RDS.

The initial setup will be complex. You and your team need to understand the complexities of setting up IAM, security groups, AMIs, VPCs, autoscaling/loadbalancing, and RDS, then plan for multiple availability zones for disaster and recovery. You also need to set up an infrastructure admin and infrastructure support team who will work closely with the AWS team. You do not want your entire development to get involved with setting up the infrastructure. Your administrators and infrastructure team need to set it up, then guide the development team on how to utilize the infrastructure.

The initial vendor team could help to set up the infrastructure, team organization, etc. Then, your in-house team can carry out the administration and support work as well as the day-to-day tasks, such as providing access, helping developers make changes, uploading to the infrastructure, performing the migration, deployment, etc. The vendor team needs to have certified, experienced consultants to set up the infrastructure.

Work with Amazon Pre-Sales team and have them present their products to your organization. They will help you to arrive at building a business case, PoCs, SLAs, contracts, etc. You will also need to set up a product support team along with the migration, deployment, and core AWS Infrastructure Administrator teams who will be essential to the success of the project.

This is where the product stands apart. You do not need to set up thousands of servers, hundreds of database, and hundreds of DBAs. You need to set up a minimal infrastructure. There is no need to pay upfront the cost of an entire data center. It is pay as-you-go. Therefore, you realize the benefits and scale up/down as needed. Amazon will provide the required capacity. This will help you to realize the ROI quickly, which helps you to keep on growing.

This has helped reduce the cost at the same time increasing the agility of the organization. Some thing which would have costed millions of dollars and nine DBAs could easily be replaced by Amazon RDS.

By using a combination of Reserve Instances and On-Demand pricing, you can reduce the cost.

The main reason to migrate to the cloud comes from moving the underutilized. Variable demand applications moving to the cloud benefit from a cost savings as well as when they move from data center maintenance to building the core business capabilities. The application migration and database migration to AWS also provides an added advantage.

For new/existing customers building new products, such as Ola, Uber, or Swiggy, instead of building their own data center first and launching the product which involves massive costs, AWS offers a better quality solution if they are unsure about whether their product will succeed in the market. They can build the product, start making money, and utilize the pay-as-you-go model. Then, they can scale the product depending on demand utilization. That appears to be the best business case for Amazon Web Services.

Whatever is to be stored, for example, any database requirements, you can use RDS, unless you need to scale it to quite a large size, RDS could be a good solution. You can still go beyond RDS, however, basically for small to medium-sized database requirements, you can always reliably use RDS as a database solution.

The first thing I like about RDS is the on-prem implementation. The time to install or set up a database environment is very fast.

The resilience, multi-zone resilience, and availability are great. We don't need to extensively create any replication services or anything that we have to worry about as DBAs. Everything is given. It's just a matter of punching in the parameters and in the background, it all that is configured. 

The initial setup is straightforward. 

It's scalable.

The solution is reliable and stable. 

If you are a very tech-savvy guy who is a DBA, there are certain limitations due to how it's been implemented. You cannot do a lot of platform-level changes if that's how it's been set up, however, it's not required actually. Those limitations have not stopped anything, not stopped us from doing anything. That said, someone more technical may not like the limitations. Platform-level changes are not allowed. 

The solution is a bit expensive. 

I've been dealing with the solution for the last eight months. 

I haven't experienced any stability and can therefore say it's reliable and the performance is good. It doesn't crash or freeze. 

I've found the solution to be scalable. 

I have worked with only three clients at the moment with RDS.

Technical support has been very good. 

The implementation process is straightforward. The instructions are very clear. Even a person with basic knowledge would be able to spin up an RDS without an issue. It's not very complicated. The parameters are simple. You can read and understand everything very easily and know what questions to ask and what parameters to consider.

One staff member is more than enough for deployment and maintenance. 

You don't need a separate staff for the RDS management. A regular person who manages the rest of the Amazon services can easily monitor it. It has a very good service called CloudWatch, Amazon CloudWatch. Through CloudWatch, everything could be monitored very, very well. All these services are auto-scale. Alerts can be automated as well. I've done this for clients. We have it configured in a way where it's very easy to maintain and manage. We don't need to continuously monitor or anything. We have set thresholds and that CloudWatch service actually helps us to do the monitoring part automatically.

Across most of the database services, it had been a little expensive. It's not only Amazon. If you look at other cloud solution providers, they have to reconsider bringing the prices down. Some clients might not be able to reap their ROI the way that the pricing has been structured for RDS services. It was quite expensive.

I'm an implementer.

I'd recommend the solution. It would be perfect for whoever starts a small or medium business. This is the go-to database they should consider.

I'd rate the solution ten out of ten.