Before  Azure Stack and the cloud solutions, many organizations followed a gradual evolution in their data processing journey. Initially, they relied on traditional data warehousing solutions like enterprise data warehouses. Over time, teams began transitioning towards big data technologies, such as Hadoop and HBase. Subsequently, they shifted their focus to Spark-based processing for more advanced data analytics. Now, the trend has moved towards cloud-based solutions, with options like AWS, Google Cloud, and Microsoft Azure offering similar capabilities. In our current organization, we've adopted Azure as our enterprise solution, making a transition from Teradata. In my past roles with a different organization, we embraced Google Cloud after progressing from big data and Spark processing. This incremental journey showcases how organizations adapt their data processing strategies to leverage evolving technologies and cloud platforms.

We use both Azure and AWS simultaneously in various areas, allowing us to offer a choice to different business units seeking cloud implementation. Both platforms work effectively, and the choice between them depends on the specific needs of the business or project. I don't see inherent advantages or disadvantages between them as they both provide similar capabilities for businesses to carry out their work. If a business is looking for streamlined processes, Azure might be the better choice, while AWS excels in highly technical enablement.

I currently use Fortinet FortiGate.

I haven't previously worked with products similar to Azure Stack since every product in our company was deployed on an on-premises model.

I have been working with different automation tools such as Jenkins. Jenkins is a good tool to start with. Being a DevOps person, I had to go with Azure ADO and Azure DevOps, which basically gives you the view of how DevOps actually works.

The reason we lean towards Azure Stack over competitors is that it offers strong integration with the public cloud, specifically Azure. Many of our clients use Microsoft 365, and this leads to a significant presence of Azure workloads. Additionally, a substantial portion of our servers run on Windows. These factors make Azure Stack a favorable choice for us. When comparing it to Nutanix, Azure Stack stands out in terms of its integration with the public cloud and, in some cases, cost-effectiveness.

There's a cloud called Virtual Stream, which was acquired by Dell EMC. Dell EMC was our partner. 

We had a Virtual Stream Cloud for mobile that we were providing to our business customers in the different big companies. In the end, we sold the cloud. It was a bit complex compared to other cloud technologies. That said, it was quite reliable, actually.

We were using an on-premise solution, but you know that an on-premise solution is not scalable with a cloud-based environment.

Both AWS and Azure are the best in the world right now. 

It all depends on what our customers need, so we use both.

We didn't change solutions. We just added it and we are still utilizing a host of other solutions, including VMware's vSAN. They both do similar things, however, if I had my choice, I would go with VMware. That's just subjective, however. 

I actually work for an integrator company that specializes in UiPath. I primarily use UiPath, but I also use Automation Anywhere and Microsoft Power Automate.

We use Power Automate, but we also use Power BI for dashboard visualization. Then there's the standard Office 365, and we do have customers who use Azure.

We switched from AWS to Azure. The main issues were costs and some bad experiences with temporary disks. This was a long time ago, so I cannot say if AWS is currently better or worse than Azure.

I have experience with AWS and I would have to say that it is more comfortable to use than Azure.

Previously, we used AWS.

I did not use other similar solutions in this category.

We didn't previously use a different solution.

Azure Stack is the first solution of this type that I am testing.

Prior to using this cloud platform, everything we had was on-premises.

Previously we used other solutions but we didn't want to use third-party outsourced companies. We have our own infrastructure.