Data Analyst at a financial services firm with 5,001-10,000 employees
Real User
Top 10
Sep 22, 2026
I have mainly used Starburst Galaxy as a query and access layer for analytical data, as my current work involves dealing with data stored across different platforms, including Hive and SingleStore. Starburst gives us a more convenient way to query that data and expose it to reporting tools such as Power BI, so it is more for accessing and querying data used for analytics and reporting. One of the main use cases I utilize is working with historical data stored in Hive and making that data available for reporting and monitoring purposes. We also use it as part of a data access layer between the underlying platforms and Power BI. The main benefit of using Starburst Galaxy as a data access layer between my storage platforms and Power BI is easier access to the data for analytics and reporting. It also helps create a more consistent access layer, particularly when working with historical data sets, instead of building separate connections and logic for every source. I would recommend Starburst Galaxy, particularly for organizations that already have data distributed across different platforms and want or need a common SQL layer for analytics. It makes the most sense when there is a real need to query data where it already lives instead of moving everything into one system. I mainly use this for an analytics and reporting perspective and would probably give it an eight out of ten. It works well for analytical use cases, at least the ones I have been involved with, and makes access to distributed data easier. There is still room for improved usability and diagnostics, especially for users who are not platform specialists. I am mainly a data consumer rather than a Starburst Galaxy administrator, so my experience is focused on querying, reporting, performance, and usability.
My main use case for Starburst Galaxy is querying petabytes of data across vast data sources, and I use a federated query engine to join data sources from different databases and then join them using Starburst Galaxy.I have different data sources, including Oracle, DB2, and a MongoDB cluster, so I join all of these data sources using Starburst Galaxy with the federated querying feature. I transform that into Iceberg using Starburst Galaxy, land it in S3 storage, convert it into Iceberg tables, and then use them for dashboarding in Power BI or Tableau.
Senior Vice President at a financial services firm with 10,001+ employees
Real User
Top 20
Apr 10, 2026
My main use case for Starburst Galaxy is to use it as a data federation tool, collect data from various data sources, and have a unified view of the data. A quick specific example of how I use Starburst Galaxy for data federation in my daily work is that I assume I need data from five different data sources, and each data source is on a different database platform, and I have information that I need for my client profile. I can pull data from all those five different data sources and have a consolidated view of the client. Those are the main use cases for Starburst Galaxy; basically, we are trying to build data products.
I use the solution for processing large simulation datasets into aggregated datasets that can either be used for real-time data analysis or stored for later analysis.
Head of Data at a financial services firm with 51-200 employees
Real User
Top 10
Aug 12, 2025
I use Starburst Galaxy to support interactive queries and dashboards. When comparing it to Databricks, which is also deployed to serve ETL pipelines, Starburst is much faster and much more friendly to non-technical employees.
Staff Data Architect at a tech vendor with 11-50 employees
Real User
Top 10
Aug 1, 2025
I use Starburst as a cost-efficient hosted option for Trino for data integration and ad-hoc analysis across a broad range of data sources. It is surprisingly useful to query SQL Server, a Google Sheet, data in a blob store, and persist it in Postgres for downstream consumption. In addition, the Galaxy platform features such as scheduling jobs, offering a data catalog, easy permission and access control management, and the strong technical support from Starburst make it a breeze to use compared to something like Athena.
Chief Architecture Officer at a computer software company with 51-200 employees
Real User
Top 10
Jul 30, 2025
I use Starburst Galaxy to connect to many Amazon S3 and RDS data sources, exposing that data for query and analysis by data engineering teams, as well as executive stakeholders in the organization. I also use the product to serve many Tableau dashboards used by different teams within the organization.
Starburst Galaxy enhances data management with fast querying, flexible data integration, and efficient cost handling, offering seamless connectivity to numerous data platforms and formats.Starburst Galaxy stands out for its exceptional query speed and flexibility, offering effective federated querying and cluster management. It facilitates connection to multiple data warehouses and supports writing to varied formats. The intuitive interface simplifies navigation and administration while...
I have mainly used Starburst Galaxy as a query and access layer for analytical data, as my current work involves dealing with data stored across different platforms, including Hive and SingleStore. Starburst gives us a more convenient way to query that data and expose it to reporting tools such as Power BI, so it is more for accessing and querying data used for analytics and reporting. One of the main use cases I utilize is working with historical data stored in Hive and making that data available for reporting and monitoring purposes. We also use it as part of a data access layer between the underlying platforms and Power BI. The main benefit of using Starburst Galaxy as a data access layer between my storage platforms and Power BI is easier access to the data for analytics and reporting. It also helps create a more consistent access layer, particularly when working with historical data sets, instead of building separate connections and logic for every source. I would recommend Starburst Galaxy, particularly for organizations that already have data distributed across different platforms and want or need a common SQL layer for analytics. It makes the most sense when there is a real need to query data where it already lives instead of moving everything into one system. I mainly use this for an analytics and reporting perspective and would probably give it an eight out of ten. It works well for analytical use cases, at least the ones I have been involved with, and makes access to distributed data easier. There is still room for improved usability and diagnostics, especially for users who are not platform specialists. I am mainly a data consumer rather than a Starburst Galaxy administrator, so my experience is focused on querying, reporting, performance, and usability.
My main use case for Starburst Galaxy is querying petabytes of data across vast data sources, and I use a federated query engine to join data sources from different databases and then join them using Starburst Galaxy.I have different data sources, including Oracle, DB2, and a MongoDB cluster, so I join all of these data sources using Starburst Galaxy with the federated querying feature. I transform that into Iceberg using Starburst Galaxy, land it in S3 storage, convert it into Iceberg tables, and then use them for dashboarding in Power BI or Tableau.
My main use case for Starburst Galaxy is to use it as a data federation tool, collect data from various data sources, and have a unified view of the data. A quick specific example of how I use Starburst Galaxy for data federation in my daily work is that I assume I need data from five different data sources, and each data source is on a different database platform, and I have information that I need for my client profile. I can pull data from all those five different data sources and have a consolidated view of the client. Those are the main use cases for Starburst Galaxy; basically, we are trying to build data products.
I use the solution for processing large simulation datasets into aggregated datasets that can either be used for real-time data analysis or stored for later analysis.
I use Starburst Galaxy to support interactive queries and dashboards. When comparing it to Databricks, which is also deployed to serve ETL pipelines, Starburst is much faster and much more friendly to non-technical employees.
I use Starburst as a cost-efficient hosted option for Trino for data integration and ad-hoc analysis across a broad range of data sources. It is surprisingly useful to query SQL Server, a Google Sheet, data in a blob store, and persist it in Postgres for downstream consumption. In addition, the Galaxy platform features such as scheduling jobs, offering a data catalog, easy permission and access control management, and the strong technical support from Starburst make it a breeze to use compared to something like Athena.
I use Starburst Galaxy to connect to many Amazon S3 and RDS data sources, exposing that data for query and analysis by data engineering teams, as well as executive stakeholders in the organization. I also use the product to serve many Tableau dashboards used by different teams within the organization.