Amazon Relational Database Service (Amazon RDS) is a database-as-a-service (DBaaS) from Amazon Web Services.
N/A
MariaDB Platform
Score 9.8 out of 10
N/A
MariaDB is an open-source relational database made by the original developers of MySQL, supported by the MariaDB Foundation and a community of developers. The community states recent additional capabilities as including clustering with Galera Cluster 4, compatibility with Oracle Database, and Temporal Data Tables, allowing one to query the data as it stood at any point in the past.
If your application needs a relational data store and uses other AWS services, AWS RDS is a no-brainer. It offers all the traditional database features, makes it a snap to set up, creates cross-region replication, has advanced security, built-in monitoring, and much more at a very good price. You can also set up streaming to a data lake using various other AWS services on your RDS.
Our installation scenario is a MariaDB cluster composed of 3 nodes to achieve high availability in the service and in this way the application that accesses the backend (MariaDB) is always working and is not down at any time.
To achieve high performance of the application when accessing the database, a MariaDB MaxScale has been mounted that acts as a proxy for queries to the database.
Automated Database Management: We use it for streamlining routine tasks like software patching and database backups.
Scalability on Demand: we use it to handle traffic spikes, scaling both vertically and horizontally.
Database Engine Compatibility: It works amazingly with multiple database engines used by different departments within our organization including MySQL, PostgreSQL, SQL Server, and Oracle.
Monitoring: It covers our extensive monitoring and logging, and also has great compatibility with Amazon CloudWatch
MariaDB does well with PHP or Python (django) in a web environment. Developers are able to work quickly.
MariaDB is extremely well documented and has a gigantic support community. If you need ask a question on how to do things you can go to many placces online and find answers quickly.
MariaDB is fast! Queries with tens of thousands of rows are quick.
MariaDB is highly compatible with Oracle's MySQL. Basically the same thing but more open and with a brighter future.
With MariaDB it is so easy to import and export data, and backups are a cinch. This saves me so much time as compared to other RDBMS.
It is a little difficult to configure and connect to an RDS instance. The integration with ECS can be made more seamless.
Exploring features within RDS is not very easy and intuitive. Either a human friendly documentation should be added or the User Interface be made intuitive so that people can explore and find features on their own.
There should be tools to analyze cost and minimize it according to the usage.
Driver Support - Some third party applications use database drivers that cause unexplained slowness with MariaDB. This can be worked around by using the MySQL drivers, but it's not clear what causes the problem in the first place.
Support - While online communities are helpful in diagnosing problems, there isn't as much professional documentation/support available for MariaDB as some of the other major database options.
Data Visualization - It would be helpful if there were more built in options for analyzing statistics and generating reports.
We do renew our use of Amazon Relational Database Service. We don't have any problems faced with RDS in place. RDS has taken away lot of overhead of hosting database, managing the database and keeping a team just to manage database. Even the backup, security and recovery another overhead that has been taken away by RDS. So, we will keep on using RDS.
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).
MariaDB is very usable and stable to be used in production settings as an alternative to MySQL. The shortcomings of SQL are present but well understood in the community, and if the decision were to be made again, I would choose MariaDB over MySQL on future projects.
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.
Yes, I would recommend MariaDB Platform support because they answer very fast and with detailed information. They also help you with the design of the storage infrastructure, not only with the maintenance problems. On the other hand, this service is a bit expensive.
Amazon Relational Database Service (RDS) stands out among similar products due to its seamless integration with other AWS services, automated backups, and multi-AZ deployments for high availability. Its support for various database engines, such as MySQL, PostgreSQL, and Oracle, provides flexibility. Additionally, RDS offers managed security features, including encryption and IAM integration, enhancing data protection. The pay-as-you-go pricing model makes it cost-effective. Overall, Amazon RDS excels in ease of use, scalability, and a comprehensive feature set, making it a top choice for organizations seeking a reliable and scalable managed relational database service in the cloud.
It did not always compete against these technologies. Most of the time, it was complementing these databases for certain use cases to help provide a much more complete database. This makes more users want to use it to explore new solutions that help users. This is our target and how [we] work with MariaDb.
MariaDB has saved us enormously on licensing compared to our previous DB software vendor.
In service, it has enabled us (speaking as the internal DB team here) to provide better service to the other teams in the company as well as our customers, with less staff.
The level of hardware required for adequate performance, in our environment, has been much lower. Those savings have been substantial, above and beyond savings on licensing and DBA staffing levels.
