I have worked with Azure tools like Azure IaaS services, virtual machines, and SQL Server, and Azure PaaS services, like Azure SQL.

J2EE Framework is good but complicated to deploy and requires more skills. It is not straightforward compared to Microsoft .NET Framework.

The product has to compete with Spring Boot.

We did evaluate at least one other option before choosing Microsoft's .NET Framework. It was JAVA Bridge, but I prefer to use Microsoft .NET Framework because I only wanted to develop for Microsoft products and Microsoft Windows. The .NET Framework is, I think, more compatible with Windows than JAVA Bridge Virtual Machine.

No.

Java SDK. Java SDK is also good but require little bit more effort.

The product has good technical support services compared to the Java Spring Boot's ecosystem. It provides centralized support, which is helpful for developers.

We did have the option to go with PHP and Joomla, but we were concerned that it may not be available after a few years. When it comes to Microsoft technology, it is more stable and because they are a giant in technology, .NET will be an everlasting solution for which we can always find developers and support.

We did evaluate other options. We looked at both Java and PHP.