What is our primary use case?
We used this product as implementers. For example, a client wanted to use the Azure stack, specifically Azure Machine Learning Studio. Microsoft was a consultant on the project, and we were the implementation partner.
There are actually two tools. One is Azure Machine Learning Designer (which used to be called Azure Machine Learning Studio), and the other is Azure Machine Learning. Designer is a drag-and-drop interface, primarily for those without extensive coding expertise.
Azure Machine Learning has become the de facto product, and it allows you to write code and provides numerous components for building machine learning models.
How has it helped my organization?
We build all our machine-learning models using ML Studio. That's the primary purpose for us. We build standard models that use data and various algorithms.
My expertise was focused on the analytics aspect. We worked in a large firm with different teams responsible for MLOps and integrating outputs with other systems.
My responsibility was to get data, build models, and provide the output. How the output was rendered and the process of doing so was handled by other teams.
Additionally, there's a separate team that handles the productionalization of machine learning models. It's a diverse team structure, so the scope of the totality of the integration process varied. Essentially, they take the model I build, use Azure DevOps for versioning, and then deploy it to production.
What is most valuable?
Everything in Azure is very intuitive. As a Microsoft product, it's designed that way. You can easily search for things, and many features are built-in. Many things can be easily done via drag-and-drop.
We often use custom code that we can template or create as boilerplate code for different teams. It sounds difficult, but Azure makes it very easy.
The learning curve is very low. Operationalizing the model is also very easy within the Azure ecosystem.
The drag-and-drop interface specifically improves our workflow a lot. Designer simplifies the process when we want to create a quick model. It makes things very, very easy. It's a great starting point.
When we want to create models, model management and deployment are crucial. We had boilerplate code ready, and Azure made it significantly easier to deploy using its services. That was the easy part.
What needs improvement?
In terms of data capabilities, if we compare it to Google Cloud's BigQuery, we find a difference. When fetching data from web traffic, Google can do a lot of processing with small queries or functions. Azure didn't have that same inbuilt feature for website traffic or analytics, unlike Google DB and BigQuery.
For how long have I used the solution?
I started using it around the year 2020. We used it up to 2023, so roughly two years.
What do I think about the stability of the solution?
It is a stable product. I would rate the stability a nine out of ten.
What do I think about the scalability of the solution?
It is a scalable solution because it works well for large databases.
I would rate the scalability a nine out of ten.
How are customer service and support?
The customer service and support are good.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
We've used Google Vertex AI and AWS SageMaker.
How was the initial setup?
I was not involved in the deployment process. But there is maintenance. It was quite a headache.
Maintenance does require attention. With any cloud implementation, cost optimization is a major factor. Our team had discussions about it.
What's my experience with pricing, setup cost, and licensing?
I would rate the pricing an eight out of ten, with ten being very expensive. Not very expensive, not very cheap.
It was on a yearly basis, and there were also usage-based costs.
What other advice do I have?
If it's my recommendation, it's a very competent product. It has all the necessary features for data engineering, data science, and model management.
It's a complete suite of products that can address your end-to-end data needs.
Overall, I would rate the solution a nine out of ten.