Microsoft Azure vs. wasmCloud

Azure is particularly well suited for enterprise environments with existing Microsoft investments, those that require robust compliance features, and organizations that need hybrid cloud capabilities that bridge on-premises and cloud infrastructure. In my opinion, Azure is less appropriate for cost-sensitive startups or small businesses without dedicated cloud expertise and scenarios requiring edge computing use cases with limited connectivity. Azure offers comprehensive solutions for most business needs but can feel like there is a higher learning curve than other cloud-based providers, depending on the product and use case.

If you want to start pivoting your legacy code into a serverless paradigm this is the platform to target. If you want to start moving away from walled gardens and back into a space where code isn't centralized, costs can be offset by utilizing customer or edge hardware this is the platform to focus on. If you want a model that will scale well past many of the existing serverless frameworks, that won't get caught up in the security weaknesses of current paradigms this is what you need to invest in. If you want modern code to interact with legacy code in a safe way that doesn't expose vulnerabilities you can't patch against wasmCloud is awesome. If you want to write simple code that can jump from cloud to cloud to the user or edge node check it out!

• Microsoft Azure is highly scalable and flexible. You can quickly scale up or down additional resources and computing power.
• You have no longer upfront investments for hardware. You only pay for the use of your computing power, storage space, or services.
• The uptime that can be achieved and guaranteed is very important for our company. This includes the rapid maintenance for security updates that are mostly carried out by Microsoft.
• The wide range of capabilities of services that are possible in Microsoft Azure. You can practically put or create anything in Microsoft Azure.

Incentivized

• Host density of workloads
• Streamlined security approach to writing code and reducing bloat
• Interoperability of modules written in different languages

• The cost of resources is difficult to determine, technical documentation is frequently out of date, and documentation and mapping capabilities are lacking.
• The documentation needs to be improved, and some advanced configuration options require research and experimentation.
• Microsoft's licensing scheme is too complex for the average user, and Azure SQL syntax is too different from traditional SQL.

• Simplified open-source model for on-boarding devs, i.e. bare host no elixir/GUI
• Home-labbers guide to wasmCloud
• Spark more community involvement for capability providers

Moving to Azure was and still is an organizational strategy and not simply changing vendors. Our product roadmap revolved around Azure as we are in the business of humanitarian relief and Azure and Microsoft play an important part in quickly and efficiently serving all of the world. Migration and investment in Azure should be considered as an overall strategy of an organization and communicated companywide.

As Microsoft Azure is [doing a] really good with PaaS. The need of a market is to have [a] combo of PaaS and IaaS. While AWS is making [an] exceptionally well blend of both of them, Azure needs to work more on DevOps and Automation stuff. Apart from that, I would recommend Azure as a great platform for cloud services as scale.

Incentivized

wasmCloud is still in the early stages of development but the product is rapidly evolving and stabilizing and I feel it will be a preferred way of deploying and managing remote, distributed applications in the future.

Incentivized

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

Incentivized

We were running Windows Server and Active Directory, so [Microsoft] Azure was a seamless transition. We ran into a few, if any support issues, however, the availability of Microsoft Azure's support team was more than willing and able to guide us through the process. They even proposed solutions to issues we had not even thought of!

Incentivized

The core team is extremely responsive in their provided channels. From slack to github issues, there is never a long wait for feedback or guidance.

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.

As I continue to evaluate the "big three" cloud providers for our clients, I make the following distinctions, though this gap continues to close. AWS is more granular, and inherently powerful in the configuration options compared to [Microsoft] Azure. It is a "developer" platform for cloud. However, Azure PowerShell is helping close this gap. Google Cloud is the leading containerization platform, largely thanks to it building kubernetes from the ground up. Azure containerization is getting better at having the same storage/deployment options.

Incentivized

Have not made a purchase yet as we are still in the POC stage.

Incentivized

The team is incredibly helpful and informative about the product - I have not needed to use their professional services thus far.

• For about 2 years we didn't have to do anything with our production VMs, the system ran without a hitch, which meant our engineers could focus on features rather than infrastructure.
• DNS management was very easy in Azure, which made it easy to upgrade our cluster with zero downtime.
• Azure Web UI was easy to work with and navigate, which meant our senior engineers and DevOps team could work with Azure without formal training.

Incentivized

• WasmCloud has massively simplified the required ops expertise needed to run modern software.