Skip to main content

Cluj Innovation Days, 19-20 March 2015 - 4 free tickets available

Cluj Innovation Days, organized by Cluj IT Cluster, is an annual regional forum aimed to consolidate the IT community and to facilitate the interaction with business partners as well as the public sector.
The first edition was described as a collusion that brought together private and public entities from the IT sector and other industries to express the need of a common agenda and present innovative ideas, develop business relations with international partners and strengthen the local IT community.
400+ participants: representatives of the Romanian Government and the local public institutions, members from the Academia, as well as delegates from foreign Embassies and international business networks.
The third edition of Cluj Innovation Days will take place on the 19th and 20th of March and its main purpose is to continue the journey that we started two years ago, by deepening the idea evolving around innovation. The event will take place at Grand Hotel Napoca.

I received 4 tickets for Cluj Innovation Days that I want to share with community. So, if you want a ticket for this conference, you need to submit a comment to this post, where you need to include your email address. Using random.org I will extract the winners that will be contacted by me directly. You can submit for this ticket until March 8th EOD. The winners will be announced in March 10th

At this event I will have a session where I will talk about IoT and Azure. If you are interested about this topic you can join my session.


Comments

  1. Sa promovam inca un pic evenimentul
    http://www.romeodonca.ro/Lists/IT_Events/IT_Events.aspx?ID=25

    ReplyDelete
  2. Congrats! Looking forward to attending! gedorin@gmail.com

    ReplyDelete
  3. This kind of event are very interesting. cipri.stupi@gmail.com

    ReplyDelete
  4. Hello. Both of you will be contacted by conference stuff. See you at the event.

    ReplyDelete

Post a Comment

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