Skip to main content

[Event] Global Windows Azure Bootcamp in Cluj-Napoca, March 29

Registration link: https://codecamp-cluj-azurebootcamp.eventbrite.com

One year ago Codecamp Romania added Cluj-Napoca on the map when we organized Global Windows Azure BootCamp, we here part of an event organized in more than 90 location worldwide.

This year, we are doing the same thing. In March 29 we will organize in Cluj-Napoca a full day of workshops related to Windows Azure. This event is part of Global Windows Azure Bootcamp, which is organized in more 140 locations registered in 56 countries.

Let’s see what will happen in Cluj-Napoca. In March 29, there will be workshops of 90 minutes, where all the attendees will have the opportunity to learn how to use different services that are available on Windows Azure. Because of this you should bring your own laptop with you and have Visual Studio 2013 or 2012, Windows Azure SDK and a free account for Windows Azure set.

The event will start at 9:00 AM with a little networking. The real coding will start at 9:30 AM with a workshop about how to deploy and hosts web sites on Windows Azure. After this we will continue with a training related to different ways how data can be persisted on Windows Azure. At the end we will try to see and understand what are the different mechanism (ways) of creating batches jobs on Windows Azure.

Registration link: https://codecamp-cluj-azurebootcamp.eventbrite.com

And don’t forget, this event is 100% free. Special thanks to our sponsors:

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