11:11 Public Cloud vs. Amazon Web Services vs. Leaseweb Managed Hosting

I honestly can't think of any that couldn't be better served by Azure.

We are using RDS for the database services. With RDS, we don't have to manage much, as most of the DBA tasks are automated. For development purposes, we are using Kubernetes pods, which makes it easy to deploy applications and scale up as needed. AWS integration with in-house applications is seamless, making it easy to keep a data-sensitive application on-premises while still utilizing AWS services.

Incentivized

• It has a great advantage for inter-team sharing
• For large data, I found it convenient.
• I have seen great structure in reports followed

Incentivized

• Starting an instance and accessing it for testing purpose, demo or production deployment its always easy.
• All the things which are available over AWS are pretty well managed and easy to use.
• You might find everything you required for an product and other development over AWS.
• Its suitable for both either an enterprise or an startup
• Various resources and documentation are available in case you struck somewhere.

Incentivized

• Convoluted support systems.
• Obstructive bureaucracy.
• Inflexible support personnel/policies unable to do what it takes to get the job done.

• The AWS Management Console can be overwhelming. so a better dashboard and organizing it would improve usability.
• The pricing models are complex. We need a more clear price calculators and cost management tools to manage our expenses better.
• Enhancements in cross service compatibility and easier third party integrations could streamline workflow.
• Simplifying model training in SageMaker and improving IAM for granular access control would make AWS more user friendly

Incentivized

I would gladly rely on AWS for any large-scale application deployment. For prototyping and small-scale applications, a more heavily managed environment on top of the 'bare metal' virtual infrastructure, such as Heroku or Elastic Bean Stalk, is probably a more productive approach in most cases

Amazon Web Services is a great tool when it comes to middle size organizations like us. It provides multiple tools and functionalities in low costs. The best feature we have to pay as we go. No financial burden on company for the unused instances. It also comes with greater level of security such as two level authorization such as multi factor authorization.

Availability is very good, with the exception of occasional spectacular outages.

AWS does not provide the raw performance that you can get by building your own custom infrastructure. However, it is often the case that the benefits of specialized, high-performance hardware do not necessarily outweigh the significant extra cost and risk. Performance as perceived by the user is very different from raw throughput.

Support is completely inflexible in their policies and procedures, turning even the simplest request into a months-long ordeal.

The customer support of Amazon Web Services are quick in their responses. I appreciate its entire team, which works amazingly, and provides professional support. AWS is a great tool, indeed, to provide customers a suitable way to
immediately search for their compatible software's and also to guide them in a
good direction. Moreover, this product is a good suggestion for every type of
company because of its affordability and ease of use.

Incentivized

The API's were very well documented and was Janova's main point of entry into the services.

I would select Sungard on the basis of technology foundation and functionality. It gave me an ample amount of features which I could use in a better way. The inter-team communication gets a better structure than the other products. I would use it on the basis of the above mentioned points. This has proven to be a good support for my team.

Incentivized

In my personal experience, AWS is superior to both GCP and Azure in the majority of usable applications. GCP suffers from the near total misunderstanding of how support system is even supposed to work, and while _some_ services are pretty nifty and well-polished, some are mindbogglingly designed black boxes with self-conflicting documentation. Some of it comes from having legacy systems, sure, but AWS somehow manages, even having a rather big lead start. Azure, from my limited experience, is limited to people somehow coerced into its usage by external constraints. That being said, IF you can design and implement something there, it will probably run fine.

Incentivized

• Positive - Inter-department report flow was quick.
• Positive - Defined process gave us a defined to finish our goals.
• Negative - Detailing on each module is less.

Incentivized

• Provisioning resources like large database instances is really quick. We can easily scale our instances up or down as per need.
• Storing files in S3 instead of onprem NAS drives is much more economical, especially for the files stored in glacier deep archive for compliance purposes.
• Backup snapshots of EBS volumes and RDS instances may increase the cost of cloud if not cleaned up properly.

Incentivized