We host various sites and utilize this solution for purchasing domains as well. It's simple to host small sites and back-end software applications on Azure instead of on regional servers
Web Developer at Indiana
This solution has the best website amongst all cloud computing platforms. It is simple to utilize, and one can release nearly anything, from app services to host sites
Pros and Cons
- "Azure has the best website amongst all cloud computing platforms. It is simple to utilize, and one can release nearly anything, from app services to host sites."
- "Establishing the account in the beginning was very difficult."
What is our primary use case?
How has it helped my organization?
It has great deals of APIs for automation that we can utilize for managing our services. We implemented some custom tools that were developed in house and are extremely happy with the time that we now spend monitoring the websites.
What is most valuable?
Azure has the best website amongst all cloud computing platforms. It is simple to utilize, and one can release nearly anything, from app services to host sites.
What needs improvement?
Being a big item, it has it's own share of bugs. I had a great deal of difficulty establishing the account at first.
Buyer's Guide
Microsoft Azure
November 2024
Learn what your peers think about Microsoft Azure. Get advice and tips from experienced pros sharing their opinions. Updated: November 2024.
816,406 professionals have used our research since 2012.
For how long have I used the solution?
One to three years.
What do I think about the stability of the solution?
No
What do I think about the scalability of the solution?
No
What was our ROI?
We are at 150% at this time, not considering the time that we concentrated on something else.
Which other solutions did I evaluate?
Yes, we searched Google and Amazon.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Solutions Architect at a tech services company with 5,001-10,000 employees
Some of the valuable features include monitoring, management, and data analytics.
Pros and Cons
- "Compute (App service, and virtual machine scale sets): The ability to manage Windows and Linus virtual machines."
- "Specifically, I would like to see better Azure Data Analytics and monitoring RF."
How has it helped my organization?
By migrating our infrastructure to Azure, we have been more agile on several fronts as an organization, from been able to create proof of concepts on the fly, to being able to make changes quickly and repeatedly.
What is most valuable?
- Compute (App service, and virtual machine scale sets): The ability to manage Windows and Linus virtual machines.
- Monitoring and Management: Ability to use log analytics to search, collect and visualize machine data from on-premises and cloud.
- Data Analytics: Security and Identity (Azure Active Directory): This feature adds multi-factor authentication, self-service password reset and group-based application access.
- Storage (Azure files): Still in preview at this stage, its allows the creating of SMB 2.1 shared folders on Azure storage service.
- Azure Site Recovery: Allows the replication and recovery of VMs hosted on Azure, thereby extending business values of almost any size.
- Networking (Azure ExpressRoute): This feature allows the connection of data center with Azure via private link that does not travel over the internet. Advantages include security, lower latency and higher reliability.
What needs improvement?
Every area of the product still needs to improve as it can always get better. Windows wasn't where it is today decades ago. There was a continuous improvement and evolutionary changes. Same is expected of Microsoft Azure.
Specifically, I would like to see better Azure Data Analytics and monitoring RF.
What do I think about the stability of the solution?
Azure is very stable with no issues at all.
What do I think about the scalability of the solution?
The ability to scale easily is one of Microsoft Azure strength, one can start and scale up as traffic increase or as the business growth is required. So we didn't have issues with scalability.
How are customer service and technical support?
The technical support is great.
Which solution did I use previously and why did I switch?
We never used a different solution. We had a PoC with every vendor in the same competitive space and decided to go with the best.
How was the initial setup?
The initial setup was very straightforward, as we knew what is required from the technical perspective and as a business. Which we specified in an architectural design before hand.
What's my experience with pricing, setup cost, and licensing?
Make use of Azure pricing calculator and you will find out that Azure Is still more reasonable that the competition and do your research, when unclear speak with your MS support.
Which other solutions did I evaluate?
We evaluated some other competitive products and decided to go with Azure as its suit and meet our business requirement.
What other advice do I have?
You need to have a clear vision of your business expectation from the product. Define your business requirements, objectives and ensure that your cloud provider can support those requirements.
Consider the cost, location, licensing, and technical capability to support and guide your organization.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Buyer's Guide
Microsoft Azure
November 2024
Learn what your peers think about Microsoft Azure. Get advice and tips from experienced pros sharing their opinions. Updated: November 2024.
816,406 professionals have used our research since 2012.
Head of IT with 51-200 employees
(Some) Best Practices for Building Windows Azure Cloud Applications
In this blog post, I will talk about some of the best practices for building cloud applications. I started working on it as a presentation for a conference however that didn’t work out thus this blog post. Please note that these are some of the best practices I think one can follow while building cloud applications running in Windows Azure. There’re many-many more available out there. This blog post will be focused on building Stateless PaaS Cloud Services (you know that Web/Worker role thingie :) utilizing Windows Azure Storage (Blobs/Queues/Tables) and Windows Azure SQL Databases (SQL Azure).
So let’s start!
Things To Consider
Before jumping into building cloud applications, there’re certain things one must take into consideration:
- Cloud infrastructure is shared.
- Cloud infrastructure is built on commodity hardware to achieve best bang-for-buck and it is generally assumed that eventually it will fail.
- A typical cloud application consist of many sub-systemswhere:
- Each sub-system is a shared system on its own e.g. Windows Azure Storage.
- Each sub-system has its limits and thresholds.
- Sometimes individual nodes fail in a datacenter and though very rarely, but sometimes entire datacenter fails.
- You don’t get physical access to the datacenter.
- Understanding latency is very important.
With these things in mind, let’s talk about some of the best practices.
Best Practices – Protection Against Hardware Issues
These are some of the best practices to protect your application against hardware issues:
- Deploy multiple instances of your application.
- Scale out instead of scale up or in other words favor horizontal scaling over vertical scaling. It is generally recommended that you go with more smaller sized Virtual Machines (VM) instead of few larger sized VMs unless you have a specific need for larger sized VMs.
- Don’t rely on VM’s local storage as it is transient and not fail-safe. Use persistent storage like Windows Azure Blob Storage instead.
- Build decoupled applications to safeguard your application against hardware failures.
Best Practices – Cloud Services Development
Now let’s talk about some of the best practices for building cloud services:
- It is important to understand what web role and worker role are and what benefit they offer. Choose wisely to distribute functionality between a web role and worker role.
- Decouple your application logic between web role and worker role.
- Build stateless applications. For state management, it is recommended that you make use of distributed cache.
- Identify static assets in your application (e.g. images, CSS, and JavaScript files) and use blob storage for that instead of including them with your application package file.
- Make proper use of service configuration / app.config / web.config files. While you can dynamically change the values in a service configuration file without redeploying, the same is not true with app.config or web.config file.
- To achieve best value for money, ensure that your application is making proper use of all VM instances in which it is deployed.
Best Practices – Windows Azure Storage/SQL Database
Now let’s talk about some of the best practices for using Windows Azure Storage (Blobs, Tables and Queues) and SQL Database.
Some General Recommendations
Here’re some recommendations I could think of:
- Blob/Table/SQL Database – Understand what they can do for you. For example, one might be tempted to save images in a SQL database whereas blob storage is the most ideal place for it. Likewise one could consider Table storage over SQL database if transaction/relational features are not required.
- It is important to understand that these are shared resources with limits and thresholds which are not in your control i.e. you don’t get to set these limits and thresholds.
- It is important to understand the scalability targets of each of the storage component and design your application to stay within those scalability targets.
- Be prepared that you’ll encounter “transient errors” and have your application handle (and recover from) these transient errors.
- It is recommended that your application uses retry logic to recover from these transient errors.
- You can use TOPAZ or Storage Client Library’s built-in retry mechanism to handle transient errors. If you don’t know, TOPAZ is Microsoft’s Transient Fault Handling Application Block which is part of Enterprise Library 5.0 for Windows Azure. You can read more about TOPAZ here: http://entlib.codeplex.com/wikipage?title=EntLib5Azure.
- For best performance, co-locate your application and storage. With storage accounts, the cloud service should be in the same affinity group while with WASD, the cloud service should be in the same datacenter for best performance.
- From disaster recovery point of view, please enable geo-replication on your storage accounts.
Best Practices – Windows Azure SQL Database (WASD)
Here’re some recommendations I could think of as far as working with WASD:
- It is important to understand (and mentioned above and will be mentioned many more times in this post :)) that it’s a shared resource. So expect your requests to get throttled or timed out.
- It is important to understand that WASD != On Premise SQL Server. You may have to make some changes in your data access layer.
- It is important to understand that you don’t get access to data/log files. You will have to rely on alternate mechanisms like “Copy Database” or “BACPAC” functionality for backup purposes.
- Prepare your application to handle transient errors with WASD. Use TOPAZ for implementing retry logic in your application.
- Co-locate your application and SQL Database in same data center for best performance.
Best Practices – Windows Azure Storage (Blobs, Tables & Queues)
Here’re some recommendations I could think of as far as working with Windows Azure Storage:
- (Again :)) It is important to understand that it’s a shared resource. So expect your requests to get throttled or timed out.
- Understand the scalability targets of Storage components and design your applications accordingly.
- Prepare your application to handle transient errors with WASD. Use TOPAZ or Storage Client library’s Retry Policies for implementing retry logic in your application.
- Co-locate your application and storage account in same affinity group (best option) or same data center (next best option) for best performance.
- Table Storage does not support relationships so you may need to de-normalize the data.
- Table Storage does not support secondary indexes so pay special attention to querying data as it may result in full table scan. Always ensure that you’re using PartitionKey or PartitionKey/RowKey in your query for best performance.
- Table Storage has limited transaction support. For full transaction support, consider using Windows Azure SQL Database.
- With Table Storage, pay very special attention to “PartitionKey” as this is how data in a table is organized and managed.
Best Practices – Managing Latency
Here’re some recommendations I could think of as far as managing latency is concerned:
- Co-locate your application and data stores. For best performance, co-locate your cloud services and storage accounts in the same affinity group and co-locate your cloud services and SQL database in the same data center.
- Make appropriate use of Windows Azure CDN.
- Load balance your application using Windows Azure Traffic Manager when deploying a single application in different data centers.
Some Recommended Reading
Though you’ll find a lot of material online, a few books/blogs/sites I can recommend are:
Cloud Architecture Patterns – Bill Wilder: http://shop.oreilly.com/product/0636920023777.do
CALM (Cloud ALM) – Simon Munro: https://github.com/projectcalm/Azure-EN
Windows Azure Storage Team Blog: http://blogs.msdn.com/b/windowsazurestorage/
Patterns & Practices Windows Azure Guidance: http://wag.codeplex.com/
Summary
What I presented above are only a few of the best practices one could follow while building cloud services. On purpose I kept this blog post rather short. In fact one could write a blog post for each item. I hope you’ve found this information useful. I’m pretty sure that there’re more. Please do share them by providing comments. If I have made some mistakes in this post, please let me know and I will fix them ASAP. If you have any questions, feel free to ask them by providing comments.
http://gauravmantri.com/2013/01/11/some-best-practices-for-building-windows-azure-cloud-applications/Disclosure: I am a real user, and this review is based on my own experience and opinions.
Manufacture at a manufacturing company with 51-200 employees
Limitless infrastructure possibilities with good reliability and a potentially quick deployment
Pros and Cons
- "The most valuable aspect of the solution is the limitless possibilities of the infrastructure."
- "Technical support needs improvement."
What is most valuable?
The most valuable aspect of the solution is the limitless possibilities of the infrastructure.
What needs improvement?
The documentation is out of date. It needs to be improved and modernized.
Technical support needs improvement.
I would like to see more flexibility surrounding what framework you can use for machine learning model creation.
For how long have I used the solution?
I've been using the solution for three years.
What do I think about the stability of the solution?
The solution is very stable. There are no bugs or glitches. it's reliable and the performance is good. It doesn't crash or freeze.
What do I think about the scalability of the solution?
The solution scales well. A company can expand it as necessary.
We have around 100 consultants using the solution.
How are customer service and support?
They do not seem to have enough technical support staff. Sometimes you have to contact them using email. You get the answer maybe three weeks after that email. It's available, however, it's not enough, and it's not very fast.
How was the initial setup?
In terms of the initial implementation, how difficult or easy it is depends on the services. The most common deployments are pretty clear and it's pretty simple, however, in some cases, it's very difficult.
The deployments can be fast. For the simplest ones, five minutes is enough. However, sometimes when you are trying to use a specific service, for example, the cloud solution, it could take days or weeks just to get it available.
What about the implementation team?
We have had a partner support us with the implementation.
What's my experience with pricing, setup cost, and licensing?
We pay a licensing fee on a yearly basis. I don't have details in terms of the exact costs. Sometimes there are extra costs here and there.
What other advice do I have?
We're a partner.
Inside the cloud, I have experience using different kinds of products like databases products virtual machines, etc.
I'd advise new users to prepare for certification. The most basic one is fine. Companies should preview the solution before they start any project.
I would rate the solution at an eight out of ten.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Disclosure: I am a real user, and this review is based on my own experience and opinions.
CEO at Finanblue
Secure, useful with incredible customization and the support is good
Pros and Cons
- "If you have large traffic amounts, Microsoft Azure will continue to provide our customers with the best storage experience."
- "The initial setup can be improved."
What is our primary use case?
We use Microsoft Azure to host our software development solutions and solutions for reproduction.
We have many solutions running alongside Microsoft Azure that are mainly for the financial sector.
We use Microsoft Azure to host and develop.
What is most valuable?
It's great! It's very useful.
It has a separate environment for developers and developers' solutions. We have environments for PaaS and quality assurance, and we also have an environment where we can lend our solutions to our customers.
We like the Azure DevOps.
If you have large traffic amounts, Microsoft Azure will continue to provide our customers with the best storage experience.
It's very secure.
Microsoft Azure has incredible customization.
What needs improvement?
It's not user-friendly because it is made for developers. A normal user can't use it, but for a developer, it is a very friendly solution.
The initial setup can be improved. It should be simplified and made easier for developers to set it up.
I would like to see the use of Microsoft DevOps simplified. It's automation to develop and deploy software that is very difficult to use. It is so complicated and we need extra time to learn it. It is not easy.
For how long have I used the solution?
I have been working with Microsoft Azure since 2016.
We use the standard S3 applications.
What do I think about the stability of the solution?
Microsoft Azure is very reliable. It's a highly stable solution.
What do I think about the scalability of the solution?
Microsoft Azure offers huge scalability. We can manage scalability automatically or manually. It is very fast and very reliable.
We have approximately 30 users in our organization who use Microsoft Azure.
How are customer service and technical support?
The service is very good. They are highly technical and provide answers to things that are not easy to apply. Before the pandemic, at least, the support was good and very fast.
We had some issues with support after the pandemic, where the replies took a very long time. Technical support could improve their response time. They should respond faster.
Which solution did I use previously and why did I switch?
We use many Microsoft tools, such as Microsoft Teams, also Skype, and Google Meet.
How was the initial setup?
The initials setup is difficult. It requires specialists.
Similar to Google Cloud and Amazon Web Services, it is complex.
It can take six to twelve months to deploy this solution.
What about the implementation team?
We had help from specialists to help with the complex setup. It is not easy for everyone.
What other advice do I have?
I would suggest calling a specialist who is certified to help with the setup and the deployment, don't do it yourself. The specialists are reliable and can deploy the solution faster.
I would rate Microsoft Azure a ten out of ten.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Microsoft Azure
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Senior System Administrator at a tech services company with 5,001-10,000 employees
Easy to use, scales well, and the technical support is good
Pros and Cons
- "This product is quite easy to use and is available on-demand."
- "There are so many services available that the interface is a little bit messy, and when you're looking for a specific service, you have to know exactly where to search."
What is our primary use case?
We are using Active Directory in Azure, so it's for all of the Office 365 services.
What is most valuable?
This product is quite easy to use and is available on-demand.
What needs improvement?
There are so many services available that the interface is a little bit messy, and when you're looking for a specific service, you have to know exactly where to search. Having better visibility in the interface would be an improvement.
For how long have I used the solution?
We have been using Microsoft Azure for a couple of years.
What do I think about the stability of the solution?
This is a stable product and we plan to continue using it.
What do I think about the scalability of the solution?
Azure is a scalable solution. We have approximately 150 users.
How are customer service and technical support?
We have used technical support and it is very good.
How was the initial setup?
As a cloud-based product, there is no installation.
What's my experience with pricing, setup cost, and licensing?
This is an expensive product.
What other advice do I have?
In summary, this is a good solution, and other than some improvements to the user interface, I cannot think of any features that are missing.
I would rate this solution an eight out of ten.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Solution Architect at a sports company with 201-500 employees
Stable with a good application gateway and helpful technical support
Pros and Cons
- "The product has been quite stable."
- "The solution should emulate what MuleSoft is doing. At the moment MuleSoft has a lot of other features compared to Azure API integration."
What is our primary use case?
We primarily use the solution as a platform for our applications and security.
What is most valuable?
The application gateway is very good.
We like the WAF feature.
The product has been quite stable.
The scalability potential is very good.
Technical support is very good.
The configuration process is very minimal and happens very quickly.
What needs improvement?
The solution should emulate what MuleSoft is doing. At the moment MuleSoft has a lot of other features compared to Azure API integration. Just the coverage of the features, for example, could improve. Azure should offer more coverage of the features.
For how long have I used the solution?
I've been using the solution for a couple of years.
What do I think about the stability of the solution?
The solution is very stable. It doesn't crash or freeze. There are no bugs or glitches. It's reliable.
What do I think about the scalability of the solution?
The solution scales very well. If a company needs to expand it, they can.
We have about 1,000 users on the solution currently.
We do have plans to continue to use the solution and may even increase usage in the future.
How are customer service and technical support?
Technical support has been good overall. They are helpful and responsive. We are satisfied with the level of service we receive.
Which solution did I use previously and why did I switch?
I don't really have experience with other solutions at this time. I typically work with Azure.
How was the initial setup?
There isn't much of an implementation process as the solution is in the cloud.
However, you do need to do some configurations in order to ensure it's set up as you need it to be. This part of the process takes a minimal amount of time.
We have about 60 to 70 people who can handle deployment and maintenance within our organization.
What about the implementation team?
While I could handle the process myself, in our case, we had a network architect handle the configuration process.
What other advice do I have?
I'm a consultant.
As we are using the cloud version of the solution, we are always using the latest version as well. It updates automatically.
I'd recommend the solution to other organizations.
I would rate the solution at a nine out of ten.
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
General Manager at a tech company with 11-50 employees
A reliable, stable, and scalable solution that meets our needs and is easy to implement and use
Pros and Cons
- "There are many useful features. We use web apps, so instead of starting a web server, we just have machines running some web services. This was helpful for us in terms of the scalability of the application. We also use Active Directory for authentication and some services for the data backup. It is a very good and reliable solution. It was easy to implement this solution. It fits very well into our plans and covers our needs to provide infrastructure in the cloud. The portal to configure new resources is very easy, and it is very easy to allocate new resources."
- "We would like it to be cheaper. As a customer, we always want to pay less."
What is our primary use case?
Our production system is on Microsoft Azure. We are using the latest version of this solution.
We have services for the data in the SQL Server database. We also have servers for our web-based applications. All transactions occur in this environment. We also have a mirror environment in Azure, which is a different cloud geographically.
What is most valuable?
There are many useful features. We use web apps, so instead of starting a web server, we just have machines running some web services. This was helpful for us in terms of the scalability of the application. We also use Active Directory for authentication and some services for the data backup.
It is a very good and reliable solution. It was easy to implement this solution. It fits very well into our plans and covers our needs to provide infrastructure in the cloud. The portal to configure new resources is very easy, and it is very easy to allocate new resources.
What needs improvement?
We would like it to be cheaper. As a customer, we always want to pay less.
For how long have I used the solution?
I have been using this solution since 2013.
What do I think about the stability of the solution?
In the past, they had some major outages, but it is a pretty stable platform.
What do I think about the scalability of the solution?
It is very scalable. It is as easy as assigning more resources, but it also depends on the architecture. If you have web apps or microservices, it is easy to implement a kind of dynamic or elastic growth. When you have a lot of activities, Azure will automatically assign more resources, which is pretty convenient.
We have around 200 users in our company, but we also have a merchant network that uses our system. This network has about 1,000 users.
How are customer service and technical support?
We had to escalate one case with the Microsoft team because we lost the connection with a data store. We got a response back within an hour of the event, and it was normal. Their service is fine in this regard. You can also have a better support contract, but what we have is enough for our purposes and needs.
How was the initial setup?
It is pretty easy. You just have to follow the step-by-step guidelines. The deployment happens almost immediately. If you need to increase or upgrade a server or have a new server, you just go to the portal and create a new resource, such as a server or a disk. It is very fast. There is no waiting time at all.
What's my experience with pricing, setup cost, and licensing?
Its price can be cheaper. Price is always an issue. We pay around $10,000 per month for all resources.
Which other solutions did I evaluate?
We are launching a new platform for software as a service. We create our software, and for a new concept and architecture, we are comparing AWS with Azure. We are exploring AWS. It is a different stack, and we don't have much experience with it. So far, we don't have a lot of information about production on AWS because the product is not live yet. It will take a couple of months to be finished.
What other advice do I have?
It is a good solution. If you have any on-premise applications, you have to be very careful about the architecture. What you don't want to do is copy what you have in your data center and put it on the cloud because there are various alternatives once you are in the cloud. Therefore, I would recommend others to review the architecture and take advantage of the features that it provides.
I would rate Microsoft Azure a nine out of ten. We are happy with Microsoft and this solution.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Microsoft Azure
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Buyer's Guide
Download our free Microsoft Azure Report and get advice and tips from experienced pros
sharing their opinions.
Updated: November 2024
Popular Comparisons
Amazon AWS
Oracle Cloud Infrastructure (OCI)
Akamai Connected Cloud (Linode)
Google Cloud
Google Firebase
Alibaba Cloud
SAP S4HANA on AWS
DigitalOcean
Nutanix Cloud Clusters (NC2)
SAP HANA Enterprise Cloud
Equinix Metal
NTT Cloud
Google Compute Engine
Skytap Cloud
SAP Hybris on AWS
Buyer's Guide
Download our free Microsoft Azure Report and get advice and tips from experienced pros
sharing their opinions.
Quick Links
Learn More: Questions:
- Gartner's Magic Quadrant for IaaS maintains Amazon Web Service at the top of the Leaders quadrant. Do you agree?
- PaaS solutions: Areas for improvement?
- Rackspace, Dimension Data, and others that were in last year's Challenger quadrant became Niche Players: Agree/ Disagree
- What Is The Biggest Difference Between Microsoft Azure and Oracle Cloud Platform?
- Which backup and recovery solution can backup Azure machines to its own (dedicated) cloud?
- Which is better - SAP Cloud Platform or Microsoft Azure?
- Which solution do you prefer: Alibaba Cloud or Microsoft Azure?
- How does Microsoft MDS (vs Informatica MDM) fit with Azure architecture?
- SAP HANA Enterprise Cloud (HEC): how to migrate to Microsoft Azure?
- Does F5 Advanced WAF work with Azure App Service?