Coming October 25: PeerSpot Awards will be announced! Learn more
Buyer's Guide
AWS Outposts vs. VMware Cloud Foundation
September 2022
Find out what your peers are saying about AWS Outposts vs. VMware Cloud Foundation and other solutions. Updated: September 2022.
635,513 professionals have used our research since 2012.

Read reviews of AWS Outposts alternatives and competitors

Robert Urech - PeerSpot reviewer
Director for Business Development at LIVING CONSULTORIA
Real User
Top 5Leaderboard
It's good for transitioning from an on-premise or hybrid setup to the cloud
Pros and Cons
  • "Azure Stack integrates well with Microsoft. It's also good for transitioning from an on-premise or hybrid setup to the cloud. It's seamless."
  • "Microsoft is changing the Azure Stack interface all the time, so it's sometimes hard to find the functionality or the service you're looking for. A feature was in one place and now it has moved somewhere else."

What is our primary use case?

We use Azure Stack primarily for hosting customer applications .NET applications. We use mainly App Service, Blob Storage, and Cognitive Services. 

We develop applications on the Microsoft platform, infrastructure, and servers. Our servers are Windows, and we use the .NET framework and C# programming language. Everything is easier in Azure.

What is most valuable?

Azure Stack integrates well with Microsoft. It's also good for transitioning from an on-premise or hybrid setup to the cloud. It's seamless. 

What needs improvement?

Microsoft is changing the Azure Stack interface all the time, so it's sometimes hard to find the functionality or the service you're looking for. A feature was in one place and now it has moved somewhere else. 

It's because the product is quickly evolving, so they're changing constantly. I understand, but it's difficult to find things when we don't use Azure every day. It's not a big issue.

For how long have I used the solution?

We've been using Azure Stack for seven or eight years.

What do I think about the stability of the solution?

Azure Stack is highly stable.

What do I think about the scalability of the solution?

We have had a good experience with scalability. Azure Stack's replication is well-written. It's flexible. For example, you can scale it differently on workdays and weekends to reduce operating costs. We automatically reduce the sizing of the solution. We stop some services like VMs on the weekends if we can. Scaling up and stopping resources is automated based on a set schedule. This is useful.

How are customer service and support?

Microsoft support is very good.

Which solution did I use previously and why did I switch?

We switched from AWS to Azure. The main issues were costs and some bad experiences with temporary disks. This was a long time ago, so I cannot say if AWS is currently better or worse than Azure.

How was the initial setup?

Azure Stack is also in the cloud, so it's easy. We also use the Internet Information Server. If you use the node server, it's going to be local and based on the technology you're using. We can choose between one or the other.

For example, we use Mongo Atlas service on Azure and on-premises. Both use the MongoDB Atlas service. It is architecture bound, so you have the choice of going through Azure or the on-premise solution because both have advantages.

What's my experience with pricing, setup cost, and licensing?

Azure is relatively expensive, but on the other hand, you get excellent support, stability, and security, so I think it's worth it. 

What other advice do I have?

I rate Azure Stack nine out of 10. It is a great tool if the technology you use is a Microsoft-based stack because Azure is Microsoft's cloud provider. 

Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
Flag as inappropriate
Buyer's Guide
AWS Outposts vs. Azure Stack
September 2022
Find out what your peers are saying about AWS Outposts vs. Azure Stack and other solutions. Updated: September 2022.
635,513 professionals have used our research since 2012.