AWS CloudFormation vs. Azure NetApp Files

AWS CloudFormation is well suited for scenarios where all of your resources need to be provisioned on AWS but it is not suited for hybrid cloud deployments. It's very easy for someone new to learn. The level of customization offered as part of the template specifically for AWS services is great. There is also a UI tool where we can drag and drop the services we want and it generates an yaml file which is very easy to use. The visibility of stacks and its resources and one place where we can track and identify the issues in deployment is great.

Incentivized

In my opinion, I would say it is more suitable to huge workloads, where you really needs the reliability and performance that a Netapp storage provides to you, larger share sizes, etc. Use cases where you really needs to store large amounts of non-structured data. It is not a cheap solution, I mean, you can find other options to store your data on the Cloud at smaller prices. So, for small companies, or companies that depends mostly on web-applications, or don't have such a specific requirements, I would not go with Azure Netapp Files.

Incentivized

• SaaS
• Paas
• Iaas
• On promises

Incentivized

• We have found that it scales very well. In some cases we had a large existing storage infrastructure and were able to migrate it while other times we started from scratch with low storage demands and Azure NetApp Files fit the bill each time.
• We have been impressed with the replication capabailities.
• The read and write speed when interacting with files is a major asset.

Incentivized

• Error Description upon Failure Needs to be Improved.
• Slow to create, delete or update.
• Need to delete resources manually. It can ask before starting deletion whether to skip those resources or delete them.

Incentivized

• It does not support file locking although its available as an add-on
• Design is far from native and has a learning curve
• We would like to have backup functionality built in so that we don't run into the issue where the replication process makes a copy of the corrupted data.

Incentivized

We didn't look into anything else as Cloudformation was "built-in" for AWS, it just kind of made sense to go with that. Terraform was something that we briefly looked into Terraform but decides to stick with Cloudformation because our task was relatively "simple". Apparently if it's a bit more complex, Terraform might be the way to go.

Incentivized

Azure NetApp Files is very well integrated with Microsoft Azure, we use the same request methods that everyone knows from Azure. NetApp and Microsoft has built a very efficient solution that allows you to transfer virtually any service to the Microsoft public cloud. Azure NetApp Files also protects our data very well.

Incentivized

• It has a positive ROI
• Less time inverted in bugs
• More stable source code

Incentivized

• The main hurdle in promoting this solution is the price. Its price definitely requires an improvement. It is more expensive than other options, so customers go for a cheaper option.
• Its security and ease of use are most valuable.
• It is stable and scalable.

Incentivized