Amazon RDS Reviews

Amazon Relational Database Service is used for spinning up test scenarios or alpha test of products. In addition, it's utilized for creating environments that may or may not be used in the long term. Excellent product for its flexibility, and lack of need for long term capital expenditures or commitments. Easy to utilize and purchase. It's a very friendly platform to use in agile environments, or in organizations that are in either an early startup mode, or rapid growth/expansion phase.

The project required many small instances across different regions and departments of our organization.

Instead of having our database servers in house, we decided to use the cloud for managing the servers. Our costs have come down with this and it's so easy to spin up a new database instance. Besides this, as we use several AWS technology we can control it with other services such as CloudWatch or Lambda.

RDS is being used in a ton of different ways, however it shines best for use in conjunction with Elasticsearch and providing the endpoint a writable position that we don't have to manage. Being multizone it allows for it to always be up and working; also since backups are automatic, it takes off that overhead of our engineering team.

I have used the Amazon Relational Database Service on behalf of a customer that was creating a mobile game that had elements of e-commerce. We needed something that was scalable, easy to implement, only charged us for the resources that we used, and had excellent customer service as this was a new project for our agency. ARDS checked every box.

We use AWS RDS to manage our MySQL and PostgreSQL databases without having to worry about issues like replication error, hardware failure or logs(general, slow, error) analysis. It is being used primarily by the database team but indirectly a lot of teams use RDS. Since RDS manages a lot of tasks for us, it frees us to focus on the business side of things.

At my current organization, we are using Amazon Relational Databases as our first option databases, supporting our DevOps environment. Currently, our monitoring system (based on Zabbix) and our configuration management system (based on Puppet) are using it as the main database. In our team, all databases are being based on AWS RDS PostgreSQL so far.

Our organization runs lean, and as a small business that means that each employee wears multiple hats. With Amazon Relational Database Service we are able to deploy, backup, migrate, and manage a vast array of database servers without the need for a full-time Database Administrator. Amazon makes things like failover and backups so easy, my 89-year-old grandmother could do it.

Amazon Web Services Relational Database Service (RDS) is being used as our production data store running MySQL. We use it to store user information, click information, billing information. Additionally, we have a separate instance running PostgreSQL and storing some of our proprietary objects used to emit streams for our core business model.

We use AWS RDS service for multiple applications as a backend for MySQL Databases. It helped us in updating MySQL versions, backups, and snapshots. We don't have to spend time managing and maintaining infrastructure, and we spent the most time on business. We can choose or readjust capacity based on demands and also automatic backups stored on S3 bucket.

Amazon Relational Database Service is used to host databases accessed by web applications that are on servers hosted within AWS EC2. There is also a database hosted in RDS used by end-user desktop applications.

We use Amazon RDS across our organization to provide website data and data for applications used internally. It allows us to have fully managed MySQL and PostgreSQL instances at our disposal without the headache of maintaining backups and doing minor upgrades manually or setting up redundancy.

We have been using AWS RDS with MySQL for internal as well as production level since 2014. Amazon RDS is the best option to host relational databases. We are using AWS RDS to support our web service and website solution for the client, which exceeds 1+ million hits over a month.

Amazon Relational Database Service is used by our Development team to centrally host data that our customers create using our application. Our customers are all within North America. Our application can use either MySQL or Amazon's Aurora, interchangeably. Amazon's RDS tools allowed us to quickly move from a distributed application with local databases on each customer's PC, to a SaaS model with multi-tenancy.

We started recently using Amazon Relational Database service in our company. We are exploring the usage and trying to utilize it at the maximum level. Still we are in the learning phase. Presently we are using Amazon Relational Database service in building reports, Analyzing the data in different ways. As I said earlier still we are in the learning phase as of now we are in good shape.

My organization uses Amazon Relational Database Service (RDS) to manage all of its Databases. The nice thing about RDS is you don't need to have a traditional Database Administrator on staff. Creating an instance of any of the many Database offerings (MySQL, Postgres, etc.) is as easy as a push of a button, and all the complexities around managing your data become very simple.

My organization has, since the beginning, utilized RDS as our transactional, day-to-day database, at first staging all incoming data in a PostgreSQL. Although it has performed so well that it now handles all of our data warehousing and has handled our heaviest queries with enviable aplomb. We had initially staged data in RDS for migration into Redshift, but have determined that running well-optimized queries on our particular volume of data--certainly not the petabytes that would justify Redshift--our PostrgreSQL database on RDS is actually more performant.

Amazon RDS is a great service for managing all of your relational database services in a simple manner. In our shift to data analytics and a cloud infrastructure for our applications, RDS was invaluable in providing consistent backend support for all of our applications, both small and large. Its ability to quickly hook up to any existing AWS infrastructure and replicate itself across multiple AZs meant that we could quickly adjust the availability and cost efficiency of an application's database as it scaled.

Currently, Amazon RDS is used as a data store for all the micro-services in my organization. It is particularly suitable because, in a very loosely coupled micro-services landscape, none of the services need a complex table structure and limited data redundancy is tolerated. Hence, a medium instance of RDS is more than capable of servicing our production-grade micro-services without the maintenance cost of an on-premise RDBMS.

Amazon RDS is our core database platform. It is used for both development and production loads, throughout the company. RDS provides us with a full-featured database without the cost of managing the server or installation.

We are using Amazon Relational Database Service to provide various managed database clusters, enabling us to have our data replicated to multiple availability zones, in addition to nightly backups, and managed updates without downtime. Since Amazon Relational Database Service supports MySQL and MariaDB, we are able to use RDS without changes to our platform, removing vendor lock-in.

We use RDS to run all the databases to run our platform for both OLTP and analytics/reporting purposes. This includes traditional PostgresSQL Aurora PostgeSQL. and Aurora MySQL implementations.

Amazon RDS is one of the primary data stores for all applications in our organisation. We also use AWS DynamoDB, Elastic Search, Redis etc apart from RDS. We preferred RDS over other DBaaS because it's a part of AWS which is highly reliable and scalable, and it is a completely managed solution which is simple, easy to use and also offers advanced features required by DevOps team.

Our company has a cloud-first and AWS first strategy that includes creating and moving databases to the public cloud. We started this journey seriously about 2 years ago and have decided to use RDS services as often as possible, instead of using EC2 instances for our database environments. While our footprint in the public cloud is still a small part of our overall compute, we are finding that RDS is meeting our database needs are we are migrating and creating new ones. RDS is not only solving issues for the operations of our business, we are also using RDS as part of our overall data lake strategy.

We use Amazon RDS as the backing data store for our various microservices as well as the utilities that manage service scheduling and system availability. Our primary databases are configured with Postgres, but our management utilities use MySQL under the hood. In production, we also use a high-availability configuration with automated failover to a backup system. This is all to say we use RDS extensively in our organization and the reliability of the platform provides both us and our customers with piece of mind.