Feed: SingleStore Blog.
Author: .
Jack, Josh and Gerry all had a similar problem — they were struggling with legacy single-node databases that could no longer keep up with the demands of their business.
Most organizations start with first-generation, open-source single-node databases (like MySQL, PostgreSQL or their commercial variants) to power their SaaS applications — quickly running into several challenges:
-
Bottlenecks with ingesting, processing and analyzing the fast-moving streaming data necessary to power modern, interactive SaaS applications
-
Lagging query performance as data or concurrency demands grow
-
Built on single-node architectures and struggles to scale as your business or users grow
-
Offers little-to-no analytical capabilities to drive fast, interactive user experiences.
Building the World’s Fastest Website Analytics Platform
One of the key selling points for Fathom was that they didn’t have to rewrite any queries — thanks to SingleStore’s MySQL wire protocol compatibility, which saved their developers weeks of work.
Fathom was also able to replace Amazon ElastiCache (Redis) as their application cache, and is using SingleStoreDB for all their caching needs, thereby simplifying their architecture and significantly driving down costs.
With customers like Comcast, Akamai and Tier-1 U.S. banks, Jack felt confident in using SingleStoreDB. The result? Fathom eliminated MySQL, Redis and DynamoDB from their data architecture, and saw a 1,000x improvement in query performance, and 60% reduction in database TCO.
And as Jack put it: “We moved all of our analytics data to the database of our dreams.”
The Need for Real Time, Every Time
Per Josh, “Amazon Redshift or Snowflake are great for storing large amounts of historical data and doing analytics. But neither database is going to meet a real-time service level agreement (SLA) for web developers, websites, or financial data. We want a delivery platform that scales to any number of users with real-time use cases, and any amount of data under the hood.”
Today, IEX Cloud processes over 2.5B API requests daily with an 8ms average response time — and a 10-15x increase in speed over their previous database.
The Desire for Speed, Scale and Performance
“We were also seeing some performance degradation in Azure SQL,” said Gerry Morgan, lead developer at dailyVest. “Not so much that our customers would have noticed, but we noticed there was some drop off in speed in our ingestion of data.”
Data volumes are growing at 36% a year, fueled by billions of transactions And in a highly competitive fintech space, every second counts. Those are seconds dailyVest got back with SingleStoreDB, executing stored procedures three times faster than Azure SQL — while reducing copy-and-restore operations from one hour to four minutes for a 90% improvement.
The performance improvements dailyVest saw with SingleStoreDB Cloud were substantial compared to Azure SQL, ranging from 12.4% to an incredible 95% depending on the type of operation. The dailyVest team was able to analyze more on the backend than before, all while achieving a 35% reduction in total cost of ownership (TCO).