Overall Satisfaction with SingleStore
At Tebex we use SingleStore to power our game analytics SaaS. SingleStore is used to power our translytical queries, given that we solely rely on one database solution. We have investigated numerous solutions in the past, which have all required running multiple database solutions in parallel. One for transactional queries and the other for analytical queries. This makes foreign keys impossible to work with, in addition to opening up to multiple points of failure if things were to go wrong. Our use case at Tebex is to give in-game creators the ability to get a better view into their game server analytics. SingleStore makes this process very easy, and the MySQL wire integration has made working with SingleStore a lot easier than the competitors we looked at.
- MySQL Integration/Wire
- Self-Managed Solution
- Analytical Query Speeds
- Ability to perform Translytical Queries
- Lower price plans for their paid solution
- A longer period of time to use the free credits
- More Node support within self-managed
- Easier to pick-up
- Less recruitment headache (more devs with SQL experience, than a proprietary language as competitors have)
- Less up-front cost/spend as a startup, not needing to spend on additional things
As mentioned in a previous question, the majority of other solutions we looked at required multiple databases to manage - which not only meant multiple points of failure, but would also be a headache when doing any form of foreign key lookups.
SingleStore has been an awesome solution for translytical queries, and has made data management a breeze. We are able to focus on our data structure, instead of worrying about database structures.
SingleStore has been an awesome solution for translytical queries, and has made data management a breeze. We are able to focus on our data structure, instead of worrying about database structures.
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.
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.
Do you think SingleStore delivers good value for the price?
Yes
Are you happy with SingleStore's feature set?
Yes
Did SingleStore live up to sales and marketing promises?
Yes
Did implementation of SingleStore go as expected?
Yes
Would you buy SingleStore again?
Yes