Microsoft Azure vs. Superblocks

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.

Superblocks is great for building internal tools for your company. We have our finances running on Superblocks, our client services running on it, as well as a lot of internal tooling for our product. You can build full-apps using their API builder, Workflow builder, Scheduled Jobs, and UI builder. All without having to handle your own infrastructure. It's meant to be one extra abstraction layer on top of other developer infrastructure tools like AWS, Vercel, etc.

• 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

Independently Invited by TrustRadius

A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info

• Easy to use User Interface builder for building internal apps
• Scheduled Jobs and Workflow builder in multiple languages
• API builder for support your User Interface for your internal apps

• 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.

• More flexibility on UI component designs

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

Independently Invited by TrustRadius

A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info

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

Incentivized

Independently Invited by TrustRadius

A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info

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

Independently Invited by TrustRadius

A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info

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

Independently Invited by TrustRadius

A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info

• 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

Independently Invited by TrustRadius

A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info

• We've saved thousands of developer hours that would have otherwise spent on maintaining infrastructure