What is our primary use case?
We have applications that are running on the PaaS platforms.
In the healthcare environment, we use Amazon AWS to run healthcare and hospitalization applications.
The end-user is largely unaware of how the backend works, so some of the services are provided by Amazon. So, where we are, some of the applications have been running since the beginning, and we have been using them. And some of the services are required by the packages we are running, so they use Amazon PaaS as a service.
What is most valuable?
In general, Amazon's performance is good.
What needs improvement?
When I try to enter the multi-cloud, they provide very poor support. Support is a concern with Amazon.
For how long have I used the solution?
I have been using Amazon AWS for a few years.
What do I think about the stability of the solution?
Amazon AWS is a stable solution, it is far more stable than some others.
What do I think about the scalability of the solution?
Amazon AWS is scalable, depending on the platforms and services that are used.
In our company, we have 50,000 employees who use this solution.
We intend to increase our users based on how the new releases go, and if the economics work out better than Google and Microsoft, we will definitely look to Amazon because Amazon can be extremely competitive at times.
How are customer service and support?
It should be faster. Unlike Google's and Microsoft's support, Amazon's support should be faster.
Which solution did I use previously and why did I switch?
We have used other PaaS clouds previously.
The hospitals were available on Amazon. We have certain hospitals that were part of the group when it first started, but there are a lot of hospitals that are in the process of being acquired. Once the setup is acquired, it is extremely difficult and time-consuming for them to bring it through one enterprise architecture. Now, it is not necessary to have services from only one cloud service provider; instead, we can have services from multiple providers, and we are working to integrate the multi-cloud.
How was the initial setup?
Essentially, you must design and optimize the architecture. It is not the most straightforward process to install. You must first design your architecture and then optimize it in relation to the services.
Earlier I used to work there, and we had a real skill shortage because we needed people who could understand and work in the cloud. When we developed centers of excellence and core competencies, people were required to work across multiple platforms, which is a challenge that we are currently working on. As a result, the real challenge now is for a team to have a multi-cloud. Now, if we can develop this talent organically, that will be fantastic. We'll spread out the support team we require. Another initiative that is being worked on is automation, automating scripts, and new technologies, which are assisting us greatly with serverless and cloud computing.
What's my experience with pricing, setup cost, and licensing?
It can get quite pricey at times. Because of the patterns we're attempting to use, it becomes very expensive. Where we can save money by using Google components or Microsoft components, we can go much cheaper.
You must pay a licensing fee, which is based on the usage.
Essentially, it is determined by how we use the services. There are sometimes are a soft service, sometimes we pay yearly, and sometimes we pay as we use it.
What other advice do I have?
Yes, I would recommend this solution. If we compare the three, I would rank Google first, Microsoft second, Amazon third, and the rest would follow.
I would rate Amazon AWS a seven out of ten.
Which deployment model are you using for this solution?
Public Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.