Skip to main content

[Post Event] Cloud Developers Day, Krakow 2018

This week I had the pleasure to discover the cloud and Azure community from Krakow. I was surprised to meet extraordinary people that are working on projects where cloud is changing the way how they do business and deliver services to their end customers.
Cloud Developers Days it is a conference that is at the first edition. Even so, there were almost 200 people that join the two-day event. There were two tracks in parallel about cloud and how Azure is changing the world.
At the event, I talked about what a team shall take into consideration on day ZERO of the project, and I was part of a Q/A session about cloud. You can find below the slides and some pictures from the event.
See you next time!

Title:
Day ZERO on a cloud project
Abstract:
In this session we will take a look on what we need to keep on our radar when we start a new project inside cloud. When not only us, but also clients are new in cloud ecosystem we need to be aware of small things that can make a different or secure the success of the project. Things like security, environment isolation and access controls are just a small part of the things that we need be aware. There will be examples from real life projects and hands-on implementations inside Microsoft Azure. After joining this session you will have an initial view on what things we shall be aware when we start a new project inside cloud.
Slides:

Pictures:




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