Skip to main content

[Event] ITCamp 2014 - Early Bird, don't miss this great offer (May 22-23 2014)

If you work in IT industry, then you should booked a ticket for ITCamp that will be held in May 22-23, in Cluj-Napoca. This is the 4th year when this great event is organized and each year the number of participants is greater, the number of session and tracks is higher and higher. Also the quality and level of sessions increased drastically every year.
As usually, ITCamp will bring in Cluj-Napoca great speakers from all over the world. If I look on the list of speakers, I hardly wait to take part of session held by Tim Huckaby, Peter Leeson, Alex Ionescu, David Gard, Tobiasz Koprowski and other valuable speakers.
This year, agenda look very interesting. We will have 4 tracks in parallel. Yes, you heard well, 4 tracks in parallel. It will be pretty hard to decide on what track you should attend. The good news is that all the session will be recorded and you will be able to watch them offline.
Personally, when I look on the agenda I already have problems because I don’t know on what session I should go. There are a lot of interesting sessions that I would like to join but are in the same time.
If you want to learn how you can manage redundancy on Microsoft Azure (for public endpoints and databases) I invite you to join my session, which will take place in the second day of ITCamp, from 09:00 AM. Even if Microsoft Azure has great out of the box support for this, we need to know how to manage and get the best of it.
In conclusion, be prepared for the best ITCamp ever and don’t forget that Early Bird is open until April 18th. Book your ticket now!


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