It is used for operations and marketing.
A solution with useful windowing features and great for operations and marketing
What is our primary use case?
What is most valuable?
The most useful feature is the windowing feature because you can select how long to keep the record in the memory. For example, you can use windowing if you want to identify a transaction based on a two-second or five-second interval.
What needs improvement?
The persistence could be better. Although ESP is designed for in-memory processing, it would be better if the solution is enhanced or improved on the persistence of the data that is kept in the memory. For example, if one server goes down and the information is stored in the memory, it is lost. Therefore, the persistence needs to be improved so that if there are more cases where the server is down, the information and data can still be intact.
For how long have I used the solution?
We used this solution from 2017 to 2021 before we migrated to open-source technology. It is deployed on-premises.
What do I think about the stability of the solution?
The solution is stable.
What do I think about the scalability of the solution?
It is highly scalable but depends on the architecture of the hardware. Since it's on-premises, it's highly dependent on the hardware component, but it is still highly scalable.
The solution is beneficial on an enterprise level. Regarding users at my company, it's being used by a small group in our marketing, IT and product teams.
How are customer service and support?
I rate the technical support a six out of ten. It is sometimes hard to reach them, and the wait time is long.
How was the initial setup?
The initial setup depends on the use case. It can be complex or straightforward and depends on the application's architecture and where it is used.
Regarding deployment, it is end-to-end deployment, and the ESP is just one of the components in the overall use case. So for the ESP, we used one developer for deployment, then handled the review for the checklist and the deployment process. It took less than an hour to deploy the ESP. It is still manual from a CI/CD perspective.
What was our ROI?
Regarding ROI, if the solution is highly utilized, then the ROI will be good. The use cases that you can make with the application are real-time.
What's my experience with pricing, setup cost, and licensing?
Regarding licensing, I believe since it's on-premises, it's on a per-core basis annual basis. I think there is also an option to license per transaction. Licensing depends on the client and may vary.
What other advice do I have?
I rate this solution an eight out of ten. Regarding advice, I think it is essential first to learn the basic information and the main purpose and strengths of the solution. You need to know the application's core functionality so that you can benefit and not just make use of the workaround. If you use the workaround, you will not receive the full benefit of the product or the application.
Which deployment model are you using for this solution?
On-premises
