Amazon Relational Database Service (Amazon RDS) is a database-as-a-service (DBaaS) from Amazon Web Services.
N/A
SingleStore
Score 9.8 out of 10
N/A
SingleStore aims to deliver the world’s fastest distributed SQL database for data-intensive applications: SingleStoreDB, which combines transactional + analytical workloads in a single platform.
Running MySQL RDS was a simpler solution than running standalone MySQL servers as the semi-managed nature of RDS saved us the need to install, maintain, secure, and backup our database servers. Using MySQL RDS was in addition to running MongoDB Atlas workloads and allowed us to …
Amazon Relational Database Service is a perfect fit for everyone who is seeking for an high-performance cloud-based database service. No matter if Postgres, Oracle, or any other type of relational database. Amazon RDS is our first choice for any kind of database requirement in the cloud. Especially I like the scalability.
SingleStore HTAP engine is well suited for real-time analytics, fast ingestion, scaling OLTP system like MySQL. When you need to run reports or perform aggregates on billions of rows and you get result in seconds, you cannot get this experience with other OLTP engines. I wish DBtLab was a little more developer and supported for SingleStore. This would allow to perform better data transformation. You can use stored procedures, but DBTLabs has become a standard for dimensional modeling in data warehousing projects. This is probably why SingleStore has trouble piercing in the data warehouse world. It is definately capable to compete with Snowflake when it comes to scalability, query performance, data compression, but Snowflake has ravaged the data warehouse market in few years and large corporations have already invested lots of money in migrating into Snowflake. The SingleStore community needs to grow. Everyone who uses SingleStore loves it.
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
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.
We wish the product had better support for High Availability of the aggregator. Currently the indexes generated by the two different aggregators are not in the same sequential space and so our apps have more burden to deal with HA.
More tools for debugging issues such as high memory usage would be good.
The price was the one that kept us away from purchasing for the first few years. Now we are able to afford due to a promotion that gives it at 25% of the list price. Not sure if we'll continue after the promotion offer expires in another 2 years.
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).
[Until it is] supported on AWS ECS containers, I will reserve a higher rating for SingleStore. Right now it works well on EC2 and serves our current purpose, [but] would look forward to seeing SingleStore respond to our urge of feature in a shorter time period with high quality and security.
SingleStore's performance is incredible. Our predictive algorithms went from taking 24-48 HOURS down to 15 minutes allowing our team to run those much more frequently. Previously, we were limited to about 60 requests per minute due to table locks. Implementing columnstore on SingleStore allowed us to receive 1000 requests per minute.
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.
Very responsive to trouble tickets - Often, I think, the SingleStore's monitoring systems have already alerted the engineers by the time I get around to writing a ticket (about 10 - 20 mins after we see a problem). I feel like things are escalated nicely and SingleStore takes resolving trouble tickets seriously. Also SingleStore follows up after incidents to with a post mortem and actionable takaways to improve the product. Very satisfied here.
We allowed 2-3 months for a thorough evaluation. We saw pretty quickly that we were likely to pick SingleStore, so we ported some of our stored procedures to SingleStore in order to take a deeper look. Two SingleStore people worked closely with us to ensure that we did not have any blocking problems. It all went remarkably smoothly.
In a few words, we are just to confortable working with oracle and sql server. Using RDS add another layer of distributed database in order to backup everything we have in case of a disaster and also complies with authorities locally and internacionally. All database we use, are local in custom servers that we maintain, but we agree to expand this.
Timescale was the biggest alternative option we looked at for SingleStore, however the requirement to learn a new syntax (due to not being SQL compatible) was our biggest pain point. Supporting a new language would require alterations to the Laravel framework, as this only offered SQL integration out of the box. This alteration would be time consuming and would limit our scope to future hiring due to the new syntax.
RDS is costly and thus small business should avoid it as it might not be worthful (in ROI perspective)
Downtime is very low and there are automated backups thus we dont have to worry much about technical stuff and can focus more on marketing and sales
Due to various automated features such as automated backup etc we dont need a huge technical team thus reducing the cost of maintaining a huge technical team ,
As the overall performance and functionality were expanded, we are able to deliver our data much faster than before, which increases the demand for data.
Metadata is available in the platform by default, like metadata on the pipelines. Also, the information schema has lots of metadata, making it easy to load our assets to the data catalog.
