I have previously used WebLogic, Tomcat, Red Hat, and JBoss. There are a lot of application servers, which we used to run on-premise. We switched from these solutions to a cloud offering. Many companies are moving to the cloud.

Apart from Microsoft Azure App Service, my company also uses the AWS serverless API solution, Amazon API Gateway, where microservices and risk APIs run. It's used side by side with Microsoft Azure App Service. As I belong to the security team, I'd always prefer Microsoft Azure App Service because it's pretty systematic, and Microsoft does checks and balances.

If you go for Amazon API Gateway, it's cheap and can give you different configurations. However, it's pretty tricky, security-wise, because you still have to enable a couple of new services for security. You cannot manage security easily on Amazon API Gateway. You still have to configure Security Hub and GuardDuty. It's tricky regarding security and data ingestion of logs because you still need to send that to Amazon CloudWatch directly.

I'm not as comfortable with Amazon API Gateway, which is another reason I prefer Microsoft Azure App Service; However, Microsoft Azure App Service is expensive, but I understand that because of its structure, schematics, easy management, and better security. It's secure by default with security-by-design parameters, and Microsoft would manage significant areas.

I am a technical architect and I have some commercial partners. I work as a system integrator. It is a software, global company that specializes in delivering cloud software, solutions, and services. As for this, I have over 25 years of experience with all stacks, including Azure, AWS, Google GCP, Oracle Cloud, and others. I was very interested in the Zimbra and Microsoft Exchange compilation because, in my opinion, based on my experience and statistics, Zimbra is not widely used in our accounting and based installation. However, one commercial customer inquired about my thoughts on Zimbra in conjunction with Exchange. It was very unfamiliar to me, which is why I attempted to conduct independent research on Zimbra solutions. Who and how are relevant to that question. I don't think we'll implement Zimbra because it's outside of our stack, but it was very interesting to get some perspective on the questions, nothing special, just vision and experience and growth.

We use what our customers requested from the Microsoft stacks, which are mostly infrastructure as a service solutions. It is a very limited number of PaaS installations or implementations, such as Aurora or Microsoft SQL, Azure SQL as a service, web applications on Azure, and so on. Of course, SaaS, such as Office 365, is a good option, but I can't say what other options aren't because the Microsoft stack is our primary commercial platform for our sources. It's fantastic; it provides us with some commercial advantages.

We recently used Azure, virtual machines, virtual networks, and virtual storage, as well as Azure IaaS Stack, Azure Virtual Machines, and Azure Storage.

Because Azure Web Services is based on the Azure IaaS Stack, it is infrastructure as a service. It's a platform as a service that's based on IaaS for some purposes, but our customers don't need the services to bring ready-to-use apps because they don't have a lot of education and institutes. Overall, Qualys solutions are not widely used in Ukraine, for example, by schools, governments, and institutes, due to commercial issues and, in particular, our notice time.

We chose Microsoft Azure App Service because the customer inquired. We are a very commercial company, and if the market or the customer did not request it, we did not provide it. If the customer requests it, we will provide it.

We tried Appian and Oracle Application Express prior to using Microsoft Azure App Service.

We switched to Microsoft Azure App Service because the customer already had an Azure license and could use it, which was not the case with Appian or Oracle. The licensing cost is much higher for those platforms and they also have their own cloud. Additionally, Appian requires the use of all three clouds. The customers are more familiar with Microsoft products. They preferred to use Microsoft Azure App Service over Oracle or Appian. They wanted to have a single solution for their entire organization and most of their work is done with Azure. These were some of the issues we faced and why we switched to this solution.

I did not previously use a different solution. We chose this solution to help improve the daily management of mobile users. 

We began using the solution due to the fact that digitalization is becoming normal now, and we have to integrate a lot of non-SAP solutions. App Services gives a lot of flexibility for us to bring data from any data source and push it to enterprise services, which we want to consume.

I have used SolarWinds along with Azure App Service for web application development.

We were using Oracle prior to Azure, but that was on-premises. When we made the transition to the cloud, the company opted for Azure.

We've tried many other options but the problem is we are using a product from a vendor and ideally, this functionality should be made available in that product. But we're using Azure App Service and then give users a temporary solution because we don't want to change the product that they are using because their mobile devices are very old. It's going to be a waste of money when they will any replace it in a year's time. It is more expensive to upgrade that product than developing something cheap on Azure App Service.