Firebolt is fast for analytical purposes. For example, we have analytical data in our data warehouse, and Firebolt can quickly query it to generate quick results. We have a specific catalog for any query, and Firebolt can generate the results much faster than other providers.

Firebolt
FireboltReviews from AWS customer
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
External reviews are not included in the AWS star rating for the product.
The Firebolt Experience
Mind-blowing performance and awesome support
Our developers are also able to write Firebolt queries with ease, and the aggregate indexes have been extremely helpful at ensuring very fast performance given our reports group on many columns at once.
Firebolt is also able to handle a very consistent "trickle ingestion" workflow which is unusual for this kind of use case but the main challenge that we faced when benchmarking other solutions. This way, we're able to ensure data in the data warehouse is never stale and all reports are pulling from the latest.
Before deciding on Firebolt, we benchmarked it against all other major competitors and in most cases it was at least an order of magnitude faster for our queries. What's been game-changing is how Firebolt powers all the reports in our platform without breaking a sweat. This means our customers get the insights they need immediately, without the frustrating wait times they experienced with previous solutions.
Outstanding speed and features at very reasonable cost, especially the new platform
============================================================
Original review:
There are so many things but for starters, it's just how fast we are able to serve up query results to applications and end users regardless of the data set size. Hugely complicated queries run like lightning fast, so much so that we've pivoted from using Firebolt just for reporting and analytics to also including it in our internal tooling for our business. Things we simply couldn't pull off otherwise without a massive scaling of our infrastructure.
The cost is simply unmatched for the levels of feature and performance. We're a small company with big ambitions but cost is still a paramount consideration. We have flexibility in controlling our costs and scaling as we see fit, which is great.
I've found that my team has generally found the syntax to be pretty easy to pick up, it shares a lot of commonality with other SQL flavors we're familiar with. And even when it stumps us, the documentation is pretty robust (unlike many software vendors we use) and their support staff has been top-notch. They even share a channel in our Slack where we get quick answers to many of our questions. Firebolt goes so far as to proactively watch our query performance patterns and shares that with me and will help us fix them.
Simply put, I work WITH Firebolt to solve our problems and limitations instead of working AROUND them like we have to with some other vendors.
============================================================
Original review:
The segregation of ingestion (or "general purpose") engines from read-only "analytics" engines is great from a granular control mechanism, especially as it pertains to cost. However that often requires bouncing of the read-only engine that services our applications to reflect changes made by the ingestion engine, causing a several minute outage. There are ways around it but this is often the case for us at this time.
Additionally, it would be great if there was a way to have stored queries accessible via the API access. Currently the query has to be passed to the API meaning that even where the same query could be used in our code, that is being duplicated and would necessitate an application deployment to make alterations. Compare that to a stored function/procedure model in our sql transaction engine and this is not ideal for a small shop that moves this quickly.
Can quickly query it to generate quick results
What is most valuable?
What needs improvement?
Firebolt's engine takes a long time to start because it needs to make engine calls. Currently, the data size of Firebolt is small. It can be increased.
For how long have I used the solution?
I have used Firebolt for two months.
What do I think about the stability of the solution?
The product is stable. Firebolt takes some time to start after a certain amount of idle time, but I have yet to face any bugs. In case of a bug, the only issue is that the engine starting time is a bit high.
What do I think about the scalability of the solution?
The solution is scalable. Our users are companies. We can disclose that our customers are either paid clients or subscription-based. They buy our solutions in-house, and different personas use them. We don't know the number of users per account because our solution is not a website.
Which solution did I use previously and why did I switch?
We have used Snowflake before. We support both. Firebolt has better performance, executing queries much quicker than Snowflake. However, Snowflake has more functionality. Depending on the client's needs, we can recommend the best option. Firebolt is a relatively new technology. Snowflake has many functionalities. Firebolt does not support unloading data to S3. There is no built-in way to do this in Firebolt. Alternatively, the data can be retrieved using API calls and loaded to S3 manually. Data can be unloaded to S3 directly using Snowflake. Firebolt significantly improves our performance over Snowflake because it takes less time to execute queries. This is especially important for our company because we use some KPIs that require fast loading times.
What other advice do I have?
One way to retrieve data from firewalls is to add query parameters to the connection string. For example, you can use the REST API to retrieve the security query. Some firewalls have been deployed to maintain them.
They have a team we can contact if we have any queries or are facing difficulties. They try to solve our issues completely. Maintenance is relatively easy. We handle QA issues from our solution, but I’ve never faced any issues related to the firewall. One thing the firewall didn't have before was the ability to support data in different reviews. Before that, the firewall didn't have query parameters. Based on our requirements, we added a new feature to add query parameters with the connection strength. We can directly specify the connection strength that we want to access data, and we can access it. I suggest using a shared HPE client for all requests to the firewall API. This would save our app a lot of SQL and memory resources. It's a backend-related solution, but it would be a good one. Overall, I rate the solution an eight out of ten.
Which deployment model are you using for this solution?
Noone can beat Firebolt.
Fastest place to store data
Review - Firebolt
Fire- Bolt - review
Firebolt is Awesome.
Its unique architecture is built around the use of low-cost storage options, which help me save money on storage costs compared to traditional data warehousing solutions.
Scalability:it is designed to scale horizontally, it adds additional compute resources as needed by me to handle larger workloads. This helps me avoid the need to invest in expensive hardware upgrades or additional data centers to handle increasing amounts of data.
A cool data warehouse tool!
- Its functions are clear and really easy to use.
- It has a cool API to send requests when using code
- It has customizables engines to adjust them to your budget.
- Currently, it doesn't allow updates on rows of tables.
Firebolt so far has been a good solution to our current goals in our business.