It's mostly for front-end widgets that we have in our applications and for some of the teams that do ad hoc reporting. We have some scheduled jobs also. So the data is consumed mostly by the stakeholders so that they can view things.
Compared to the other experience that I have had with other reporting tools, it is faster. That load time for the dashboard to open is way faster, no matter how big the data is. That is something that I found really helpful.
The scalability is good.
The most difficult thing I found is that it only deals with the files and does not have direct connectivity to databases. If we have 10 million rows in the data and every time the only option we have is to do a selection on the database and dump it into a file and then load that file, that's not ideal. There should be another way around it. It causes redundancy of data.
There are many other tools and they do have other connectors for other legacy systems or other databases. That functionality should be there in ThoughtSpot. There should be direct connectivity to the database. That would reduce a lot of redundancies.
The stability could be better. It takes up to 24 hours for a change to register.
I've been using the solution for ten months.
Most of the time it is stable. That said, I have faced a few incidents. For example, I was making a change in one of the reports where I introduced a new column, introduced a new table, and joined it. After that, the indexing stopped, and it took 24 hours after the indexing engine was restarted to get going. And after that, users were only able to pull that particular column that was introduced using a join. That is a very common issue that we face every day. It is kind of weird. It is really time-consuming just to wait for 24 hours before that column becomes available due to indexing being an issue in ThoughtSpot.
If someone is making changes on a daily basis, it may not be that stable.
I am not working directly on the front-end development, I'm doing the development of the back end, adding the columns, new tables, and new joins. Consumers are the end users. If it is taking 24 hours for a change to go live, then that is a really serious issue.
I have yet to face an issue scaling the data.
We have about 5,000 people using the solution. It is a combination of end users, stakeholders, and developers.
The solution was set up well before I joined the company, and therefore I was not a part of the initial setup.
I don't have any experience with how long a deployment would take.
I don't have any details in relation to pricing.
I'm not sure if other solutions were evaluated or why this solution was chosen. I was not at the company when the decision was made.
We are end-users.
I'm not sure which version of the solution I'm using. It is the latest version.
I'd recommend the solution. It's a fast business intelligence tool. However, they should now expect the same functionality as they would in other reporting tools.
I would rate the solution six out of ten.