STORM Reviews & Product Details

I really appreciate STORM for its smart information organization feature, which sorts messy raw data and materials automatically, making it easy for me to find things. I also value how STORM weaves fragmented info together and links related content, speeding up the process of sorting out the project context without me having to piece things together manually. Its seamless sync with Google Drive is a great asset, ensuring all categorized docs are stored securely in the cloud and accessible anywhere. The setup was straightforward, thanks to a clear onboarding guide, and I managed to get everything sorted in about 10 minutes without confusion. It's boosted our team's efficiency significantly. Review collected by and hosted on G2.com.

The smart organization feature doesn’t handle professional industry terms super well, it sometimes misclassifies technical documents and I have to manually adjust the categories afterward. There's also a small issue with slow processing for large batches of files. Review collected by and hosted on G2.com.

The most valuable feature of STORM is its Multi-Perspective Question Asking. It's innovative because it simulates a conversation between different AI agents with personas such as a scientist, an ethicist, or an economist, which leads to comprehensive and balanced reports. This feature automates discovering different viewpoints and provides a 360-degree view of a topic, making it an ideal tool for generating in-depth, Wikipedia-like reports. I also appreciate how STORM is designed to be highly modular and integrates well with several AI tools and frameworks for research, retrieval, and generation. Review collected by and hosted on G2.com.

While STORM is a powerful tool for generating Wikipedia-like articles, it has several documented limitations and areas for improvement, primarily regarding the quality of the final output, source bias, and operational constraints. Review collected by and hosted on G2.com.

The attendance sheet - how the structure of leave mentioned according we can make the future plans.

Documents storage, where soft copies are stored so we can easily access them.

Also, there is this easy use, and change of bank details in case of any emergency changes to be made in bank details can be done. Review collected by and hosted on G2.com.

As there are so many good features, only a very few details about the profile is required, and also, if there is a slight change in how the system works towards the login can make it better. Review collected by and hosted on G2.com.

We chose it because it is an e-commerce platform where we can implement the workflows and processes we want. Since we sell things to people with e-commerce, as people's expectations change, it is very valuable that we can implement these changes thanks to STORM. Review collected by and hosted on G2.com.

It would be better if they had the flexibility to customize accounting matters in some countries. For example, it would be better if they have integration capabilities with official invoice and payment processes in Turkey. Review collected by and hosted on G2.com.

The system has a colorful interface, easy access on the dashboard, multiple sections, and proper organization for all possible queries. Tax, attendance, and payroll information are easily accessible on the dashboard. Review collected by and hosted on G2.com.

Only a few options available. Marking attendance was very time-consuming. Too many sections available. The flowchart was not very informative. All information not available on one platform. Review collected by and hosted on G2.com.

Since people are important in e-commerce processes, it is very important that the e-commerce system for human expectations is also customizable. Storm also provides this convenience and we can set up and implement our e-commerce processes as we wish. Review collected by and hosted on G2.com.

Integration with different software is also important, but we did not use it much. If there is a need for integration with 3rd party software, you can do these as well. Review collected by and hosted on G2.com.

I like how they work since they switch things up quickly to attract customers as the competition grows.It has a good topology-defining architecture. able to handle dispersed processing. Topologies are simple to define. Compared to spark, it performs well. Nimbus had a single point of failure at first, but it has been resolved in recent revisions. Review collected by and hosted on G2.com.

There isn't really anything to dislike; they simply kind of charge a lot for their services in terms of cost.The administration of worker processes becomes problematic as the number of worker processes rises. Logs must be correlated in order to determine what went wrong.

The amount of threads that we can give each bolt is challenging to manage. Review collected by and hosted on G2.com.

It's easy to use and you'll get best results from it for your e-commerce business and websites. It'll increase your business on different levels you can't even think. Review collected by and hosted on G2.com.

Some of its features are hard to use and some of it's paid features are high maintenance for small businesses. But if you use it properly you'll achieve your goals. Review collected by and hosted on G2.com.

I like the way they do the work ,they rapidly change to gather customer attention as the competition is gradually increasing. Review collected by and hosted on G2.com.

There is kinda nothing to dislike , it's just the pricing , they kinda charge alot for their services. Review collected by and hosted on G2.com.

It has a good architecture to define the topology. Good with distributed processing. Topologies can be easily defined. It has good performance compared to spark. Initially nimbus was single point of failure, now with latest releases its been fixed.

With storm ui we can view the topology.

Storm provides the good way to manage parallelism and also scale without affecting / restarting existing eco system, user just need to add the worker processes. Review collected by and hosted on G2.com.

When topologies become complex its difficult to debug. Its difficult to visualize also. When we deploy in distributed environment it has issues with performance as tuples are transferred between the worker processes over network, need to be very careful with this aspect.

When number of worker processes increase it has issues with management of worker processes. Have to correlate logs to identify what went wrong.

It is difficult to deal with the number of threads which we can assign to each bolt. Review collected by and hosted on G2.com.