Starburst vs Trino

“Since Starburst is programmed to scale quickly and that would be a critical point in our tech stack, I felt prudent to migrate to an enterprise version – especially because of the 24/7 support and all the features that Trino offers.”

– Bruno Worisch, Lead Data Architect

 “When we introduced Starburst and Trino, we were able to instantly bring together all these different data sources and federate our queries, so we were able to reduce our time-to-insight/ Anything that was low priority dropped from three to four months to three or four days. The more urgent programs went from a couple of weeks to a couple of days.”

– Shen Wang, Principal Data Engineer

“When you consider all of those parameters together, (scalability, manageability, performance, data lake analytics, external platform connectivity) that’s what Starburst gives us. While other solutions, such as Databricks, were considered, none were as seamless and performant as Starburst, the fully supported, production-tested and enterprise-grade distribution of open source Trino.”

– Patrice Linel, Senior Manager of Data Science & Data Engineering

“We have gotten very good feedback from our users. With Trino, queries are now faster, and users can see the difference… The decision to deploy Starburst Enterprise was made simpler because it has proven to be a reliable, fast, and stable query engine for S3 data lakes.”

–  Alberto Miorin, Engineering Lead

“The needs we were struggling with was exactly why we ended up with Trino, and Starburst was a very natural next step for us as an Enterprise company – it makes data access easier, better, more supported, more stable, and more developed without needing to put the resources in place.”

– Richard Teachout, CTO at El Toro