(Post Event) Global AI/ML Bootcamp, Cluj-Napoca, 2018

This week we hosted the Global AI/ML Bootcamp event in Cluj-Napoca. We had a day full with hands-on labs on Cognitive Services and bot framework.
It was a lot of fun to compare Trump face with our faces using Vision services offered by Microsoft over Cognitive Services. More than 30 people, joined the event and discovered how Azure can improve our day to day life using AI and ML.
The event was possible with the support of our local sponsor 8X8 that hosted the event and made the event possible.

At this event, I delivered a workshop about Cognitive Services. Together with the attendees, we develop an application that is able to detect people in pictures. On top of this, the application is able to identify images where the same person appear.

You can find below slides and content from the event.
Title: Building a Computer Vision Application Leveraging the Custom Vision Service
Trainer: Radu Vunvulea
Slides:

Content: https://goo.gl/kZJZG9

Title: How to design, build and deploy your first enterprise-grade chatbot using Microsoft Azure and the Microsoft Bot Framework
Trainer: Silviu Niculiță
Slides: TBD

Comments

How to audit an Azure Cosmos DB

In this post, we will talk about how we can audit an Azure Cosmos DB database. Before jumping into the problem let us define the business requirement: As an Administrator I want to be able to audit all changes that were done to specific collection inside my Azure Cosmos DB. The requirement is simple, but can be a little tricky to implement fully. First of all when you are using Azure Cosmos DB or any other storage solution there are 99% odds that you’ll have more than one system that writes data to it. This means that you have or not have control on the systems that are doing any create/update/delete operations. Solution 1: Diagnostic Logs Cosmos DB allows us activate diagnostics logs and stream the output a storage account for achieving to other systems like Event Hub or Log Analytics. This would allow us to have information related to who, when, what, response code and how the access operation to our Cosmos DB was done. Beside this there is a field that specifies what was th...

Why Database Modernization Matters for AI

When companies transition to the cloud, they typically begin with applications and virtual machines, which is often the easier part of the process. The actual complexity arises later when databases are moved. To save time and effort, cloud adoption is more of a cloud migration in an IaaS manner, fulfilling current, but not future needs. Even organisations that are already in the cloud find that their databases, although “migrated,” are not genuinely modernised. This disparity becomes particularly evident when they begin to explore AI technologies. Understanding Modernisation Beyond Migration Database modernisation is distinct from merely relocating an outdated database to Azure. It's about making your data layer ready for future needs, like automation, real-time analytics, and AI capabilities. AI needs high throughput, which can be achieved using native DB cloud capabilities. When your database runs in a traditional setup (even hosted in the cloud), in that case, you will enc...

Azure Service Bus - How to extend the lock of a message | RenewLock

In this post we will discuss about Azure Service Bus Topics and Queues, with a special focus on Peek and Lock feature. Introduction Azure Service Bus is a messaging system that allows us to send messages between different systems in a reliable and easy way. A lot of concepts from ESB are implemented by Service Bus, allowing us to do do magic stuff with messages. There are two ways to consume messages from Service Bus Peek and Lock - locks a message for a specific time internal and notify Service Bus when we want to mark the message as processed (removed from Service Bus) Receive and Delete - once a message is received from Service Bus, it is also deleted automatically from the messaging system Peek and Lock When using Peek and Lock, by default we lock the message for 60 seconds. This means that in this time interval the message is not available/visible for other consumers. Once we process the message we can mark it as processed. If we don't mark the message as processe...

Cloud as a Story - Vunvulea Radu

Search This Blog