Skip to main content

[Post Event] WeAreDevelopers World Congress, Berlin 2022

 What a week! 

In the last 2 days, I had the opportunity to join the biggest conference for Developers from Germany - WeAreDevelopers World Congress. The number of attendees was over 8000, making me remember the good old times before 2020 when I used to join conferences with around 20-30.000 attendees.

Most of the time I spend in the expo centre, discussing with companies about their products, challenges and how they adopt cloud inside their organization. As we can imagine, Docker, Kubernetes and cloud is part of the DNA of most companies, from small startups to larger enterprise with more than 300.000 employees.

Drawing the line after 2 days of networking about the cloud, I can say that:

- 75% of the companies that were at the congress are using AWS

- 20% of the companies that were at the congress are using AWS and Azure

- 10% of the companies that were at the congress are using Microsoft Azure

- 10% of the companies that were at the congress are using Google Cloud

-  5% of the companies that were at the congress are not using a cloud vendor

Most of the companies were using Java or JavaScript or were startups. This might explain the above number. 

I received interesting feedback when I was trying to understand why they adopted Microsoft Azure, AWS or Google Cloud. The answer was, 'I don't know', it was a decision at the management level, and they were not aware of any technical assessment done before selecting the CSP (Cloud Service Provider). Nevertheless, from the development point of view, were OK - they don't care too much what cloud vendor it is used as long they have access to Kubernetes and 'Spring Boot'.

Another topic that I tried to cover was cloud governance and adoption level. Most companies are more on the reactive side. Security and cloud resource management are two dimensions covered only at the surface. They are considered part of the DevOps responsibility - even if developers can have a high impact on this. The same thing is related to cloud economics, where cost optimization is' not needed' as long as the consumption is under the allocated budget. Of course, CI/CD pipelines and IaC are part of daily work. 

What is my conclusion after these two days?

We should invest more in cloud up-skilling of development teams, and Cloud Adoption and Governance need to become mandatory. A Cloud Center of Excellence should not be ignored, and needs to be part of the cloud journey.

Cloud Adoption Framework and Well Architecture Framework should be part of the cloud journey and can have a high impact on how cloud services are used and integrated into the business. 

What about my session?

My talk was about cloud development tools for Microsoft Azure. I shared my experience and the tools I prefer to use during the development lifecycle. It was a great experience, and people found useful the tools I was talking about useful. You can check below the presentation deck. 

Let me know via Twitter or LinkedIn if you have questions or would like to propose additional tools. 

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