What is our primary use case?
We use the tool to maintain workflows on behalf of our customers. We use it in the medical field, particularly in public health and government healthcare. However, our primary role is maintaining and developing the solution for our clients rather than using it internally.
What is most valuable?
The security of the managed workflow and the managed services are the best features for us. Since we inherited their security model and it's all managed services, those are the key benefits for our clients.
What needs improvement?
The solution can become expensive if you are not careful.
For how long have I used the solution?
I have been using the product for three years.
What do I think about the stability of the solution?
I rate the solution's stability an eight point five out of ten.
What do I think about the scalability of the solution?
The tool is as scalable as you need it to be. We're not in the petabyte range yet, but we've scaled it up by over a hundred with a couple of customers. In terms of data, we're looking at hundreds of gigabytes to hundreds of terabytes. So, it's been highly scalable.
How was the initial setup?
Amazon EMR's deployment ease is five out of ten. I rate it so because of our lack of understanding and training. It was not difficult. The timeline depends on our client. We typically schedule about a six-week deployment. We've done it in as little as two weeks, but six weeks is probably the average for getting things up to speed.
You would need four to six resources to handle it. We have solution architects, security SMEs, and business process engineers. In the background, we also have developers. The main roles are solutions architect, security architect, and business process engineer.
We have a staff of about nine people, but that's spread across several clients. We probably have a couple of people working part-time for our smallest client. None of our staff are dedicated full-time to any single client. We maintain and develop the solutions with these nine staff members, occasionally calling in extra help as needed.
What was our ROI?
Based on customer feedback, the return on investment has been high, especially for those who have used on-premise systems previously. They're likely seeing an ROI of at least two to one on their investment, sometimes even more.
What's my experience with pricing, setup cost, and licensing?
I rate the tool's pricing a five out of ten. It can be expensive since it's a managed service, and if you are not careful, you can run into unexpected charges. You can make a mistake that costs you tens of thousands of dollars. That's happened to us twice, so I'm sensitive to it. We're still trying to work on that. Our smallest client probably spends a hundred thousand dollars yearly on licensing, while our largest is well over a million.
What other advice do I have?
I'm very impressed. It's certainly a contender. I don't keep up much with the current competition, but we've enjoyed the experience with Amazon, and they've been very supportive. So we get a lot of attention from them, which biases me toward a high recommendation for Amazon EMR. I rate it a seven out of ten.
We're focusing on AI integration now, especially on Amazon. It was complicated, but they're doing a great job, especially with Sagemaker. We've been building large learning models, and the most significant thing for us has been applying these models to proprietary data on Amazon. They're focusing on that aspect.
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Amazon Web Services (AWS)