Skip to main content

[Post Event] Global Azure Virtual 2020

During these times, delivering sessions remotely started to become a normality. Global Azure Virtual 2020. It was fun and a little challenge to deliver them in front of my laptop, without having the ability to be in a real venue. I love to interact with people and the social distance makes things difficult.
Last week I had the great opportunity to deliver 3 sessions during
In a few days, the recording will be made available, but until then you can find below the topics that I covered. Than you for joining the event.

Airplane buddy matching using Azure Form Recognizer
Let's dive into the computer vision world by designing a system that can analyse the flight tickets and identify the other co-workers that will fly to the same destination as you. To be able to build such a system we will use the power of Azure Cognitive Services and Form Recognizer.

Demystifying messaging communication patterns
Kubernetes together with microservice architecture provides perfect support for the new generation of software solution. Even so, Kubernetes clusters need no be able to communicate between each other or to integrate with external systems. In this session, we will tackle patterns that can be used to provide a high-redundancy and high-available communication channel, that support the powerful backend provided by Kubernetes. Keywords: Kubernetes, AKS, Service Bus, Redis, KubeMQ.

Developer Tools for Microsoft Azure
During this session, we’ll take a look at the proactivity tools that can be used to improve our development experience on Azure. We’ll talk about tools from multiple areas like storage, computation, automation, cleaning and many more. All of them are free to use, build by the Azure community or Microsoft to improve the cloud experience.

Comments

Popular posts from this blog

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(

Azure AD and AWS Cognito side-by-side

In the last few weeks, I was involved in multiple opportunities on Microsoft Azure and Amazon, where we had to analyse AWS Cognito, Azure AD and other solutions that are available on the market. I decided to consolidate in one post all features and differences that I identified for both of them that we should need to take into account. Take into account that Azure AD is an identity and access management services well integrated with Microsoft stack. In comparison, AWS Cognito is just a user sign-up, sign-in and access control and nothing more. The focus is not on the main features, is more on small things that can make a difference when you want to decide where we want to store and manage our users.  This information might be useful in the future when we need to decide where we want to keep and manage our users.  Feature Azure AD (B2C, B2C) AWS Cognito Access token lifetime Default 1h – the value is configurable 1h – cannot be modified

What to do when you hit the throughput limits of Azure Storage (Blobs)

In this post we will talk about how we can detect when we hit a throughput limit of Azure Storage and what we can do in that moment. Context If we take a look on Scalability Targets of Azure Storage ( https://azure.microsoft.com/en-us/documentation/articles/storage-scalability-targets/ ) we will observe that the limits are prety high. But, based on our business logic we can end up at this limits. If you create a system that is hitted by a high number of device, you can hit easily the total number of requests rate that can be done on a Storage Account. This limits on Azure is 20.000 IOPS (entities or messages per second) where (and this is very important) the size of the request is 1KB. Normally, if you make a load tests where 20.000 clients will hit different blobs storages from the same Azure Storage Account, this limits can be reached. How we can detect this problem? From client, we can detect that this limits was reached based on the HTTP error code that is returned by HTTP