AWS Fargate vs. Microsoft Azure

If you need to deploy Docker containers, Amazon Fargate is a very good fit. It integrates very well with other AWS services like RDS, EFS, and Secrets manager. You can have a very robust application using those services. In case you have many containers to deploy, it is however more expensive
that if you use other services like ECS or EKS, since they allow you to
share the same infrastructure to deploy multiple containers.

Incentivized

Actually, migrating to Microsoft Azure is a good solution for almost any situation, especially when all components of your network are ready to become cloud-based. The only drawback I personally encounter frequently is that older software packages cannot always be easily picked up and moved to Microsoft Azure in an optimal manner.

Incentivized

• scalability
• ease of use
• agility to up or downsize

Incentivized

• Azure simply provides end to end life cycle. Starting from the development to automated deployment, you will find [a] bunch of options. Custom hook-points allow [integration] on-premise resources as well.
• Excellent documentation around all the services make it really easy for any novice. Overall support by [the] community and Azure Technical team is exceptional.
• BOT Services, Computer Vision services, ML frameworks provide excellent results as compare to similar services provided by other giants in the same space.
• Azure data services provide excellent support to ingest data from different sources, ETL, and consumption of data for BI purpose.

Incentivized

• can't think of any

Incentivized

• In our experience, Azure Kubernetes Survice was difficult to set up, which is why we used Kubernetes on top of VMs.
• Azure REST API is a bit difficult to use, which made it difficult for us to automate our interactions with Azure.
• Azure's Web UI does a good job of showing metrics on individual VMs, but it would be great if there was a way to show certain metrics from multiple VMs on one dashboard. For example, hard drive usage on our database VMs.

Incentivized

We have been very satisfied with Windows Azure and now a lot of our business depends on it as more teams are now deploying their applications into Azure. Our next step is to have our Infrastructure team move their resources to Azure. It will take awhile for that to happen but we are positive that it will.

Incentivized

It's a very practical service to use. If you need to deploy any application with a Database, disk storage, you're pretty much set.

Everything around that can be taken care of using other AWS services. Like secrets manager, certificate manager, RDS ...

And the CI/CD part is also very easy to setup, you only need on AWS CLI command to trigger a deployment, and done !

Incentivized

Microsoft Azure's overall usability has been better than expected. Often times vendors promise the world, only to leave you with a run-down town. Not the case with our experience. From an implementation perspective, all went perfect, and from the user-facing experience we have had no technical issues, just some learning curve issues that are more about "why" than "how"

Incentivized

It has proven to be unreliable in our production environment and services become unavailable without proper notification to system administrators

Incentivized

AWS provides different support tiers. They are usually very reactive and are able to help solve the issues very quickly.

As for everything, the higher the support tier you get, the better and faster support you get.

If you're also a part of big company, you probably have solution architects at your disposal to help you with any inqueries.

Incentivized

Support is easy with all the knowledge base articles available for free on the web. Plus, if you have a preferred status you can leverage their concierge support to get rapid response. Sometimes they’ll bounce you around a lot to get you to the right person, but they are quite responsive (especially when you are paying for the service). Many of the older Microsoft skills are also transferable from old-school on-prem to Azure-based virtual interfaces.

Incentivized

As I have mentioned before the issue with my Oracle Mismatch Version issues that have put a delay on moving one of my platforms will justify my 7 rating.

We found the extra cost saved us frustration and time and ultimately money in the long run

Incentivized

I feel that Microsoft Azure typically outperforms Google Cloud Platform in hybrid cloud capabilities, integration aspects, and, primarily, security compliance features. Azure offered superior integration with Microsoft's enterprise software ecosystem, and it's second to none in my opinion. This made it the natural choice for most, especially if heavily invested in Windows, Office 365, or Active Directory deployments. We chose Azure over GCP because we simply needed Windows workload support as a strong driver, more access to global regions, and let's not forget that most tech teams in an organization are Microsoft Certified, which makes skillset transfer from on-prem to cloud a minimal learning curve over shifting to a different provider.

• easier to optimize our computer costs
• transition from server to serverless was easier once we decided to adopt Fargate

Incentivized

• Times and growth went into it. By balancing on-premises maintenance with continuous cloud improvements, we’ve budgeted and planned endlessly increased capacity.
• In today’s world of cyber-crime, clients can put even more faith in what they’ve heard. We built an innovative single-sign-on hub for all users. Also, other business platforms use Azure application gateways, reducing worker switching time and increasing productivity.
• Its step can automate to improve the investment. In addition, we can integrate our organization’s credentials into an authorization for other systems.