Skip to main content

[Event] Global Azure Bootcamp in Cluj-Napoca, April 25

Registration link: https://www.eventbrite.com/e/cluj-napoca-global-azure-boot-camp-tickets-16118725542
ITCamp is organizing the 3rd edition of Global Azure Bootcamp in Cluj-Napoca. This year we plan to play with Event Hub, Stream Analytics, SQL Replication and to discover how we can create our own Azure Datacenter using Azure Pack.
The event will take place at ISDC Office and is sponsored by ISDC (offering a great place where we can play with cloud) and RIA that will offer us all the sugar that we need to be able to discover the power of Azure.
This event is very different from the other one because you need a laptop and Azure subscription. Why? Because there are hands on labs that will be done by all attendees.

IF YOU WANT TO JOIN THIS EVENT THAT FALLOW THIS LINK AND REGISTER.
Registration link: https://www.eventbrite.com/e/cluj-napoca-global-azure-boot-camp-tickets-16118725542
See you in April 25!

What is Global Azure Bootcamp?
Welcome to Global Azure Bootcamp! On, Saturday, April 25, 2015 we are out to set some records again! In April of 2013 we held the first Global Windows Azure Bootcamp at more than 90 locations around the globe! In March 2014 we topped that with 136 locations! This year we are again doing a one day deep dive class to help thousands of people get up to speed on developing Cloud Computing Applications for Azure. In addition to this great learning opportunity we will have another set of hands on labs. In 2014 we pooled a huge global compute farm to perform diabetes research. This year everyone can participate in a compute pool for breast cancer research!

Agenda:
09:00-09:30 - Hello Coffee (wake up call)
09:30-11:00 - Ingest Telemetry data using Event Hub (Radu Vunvulea)
  • Create and Manage Event Hub
  • Send telemetry data to Event Hub
  • Consume new telemetry data using Consumer Groups
  • Consume old telemetry data using time cursor
11:00-11:45 - Process Telemetry data using Stream Analytic (Radu Vunvulea) 
  • Create a job that save all telemetry data from Event Hub to a blob storage
  • Create a job that filter telemetry data and raice alerts
  • Consume and process alerts
  11:45-12:30 - SQL Replication (Radu Vunvulea)  
  • Create and populate the main database
  • Configure two replicas
  • Access in read-only mode a secondary replica
  • Measure how long it takes for data to replicate in all nodes
12:30-14:00 - Create your Datacenter in Microsoft Azure (Adrian Stoian)
  • Create an Azure Virtual Network
  • Create a Virtual IP Address Gateway for the VPN
  • Create a Tenant VM in the VNet
  • Create a SQL Server in the VNet

Companies that sustain us:
ISDC Logo
RIA

Comments

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