Skip to main content

Global Azure Bootcamp Cluj-Napoca | ITCamp Community

This is the 4th year when we host Global Azure Bootcamp in Cluj-Napoca. Below is the invitation for Romanian colleagues.
See you there!

Acesta este al patrulea an când organizăm Global Azure Boot Camp. Acesta este un eveniment la nivel global care are loc în peste 136 de locaÈ›ii. Ca È™i anul trecut, Clujul nu se lasă mai prejos È™i apare pe harta  Azure. Pe data de 16 Aprilie vă invităm pe toÈ›i la acest eveniment din Cluj-Napoca, care v-a conÈ›ine 3 workshop-uri.
Participarea la eveniment este GRATUITĂ, așa cum a fost și până acum la orice eveniment organizat de comunitatea ITCamp. Pe data de 16 Aprilie ne propunem să avem 3 workshop-uri de câte 90 de minute fiecare, unde putem să învățăm împreună cum să folosim diferite servicii Azure. Fiecare workshop conține o parte teoretică și una practică. Din această cauză, o să aveți nevoie de un laptop.
De ce aveți nevoie:
Dacă doriți puteți să vă grupați în grupuri de 2-3 persoane la același laptop.
 
Program:
09:00-09:30 - Sosirea participanților
09:30-11:00 - Azure Service Fabric in Action (Radu Vunvulea)
  • Create our first microservice and deploy in our local cluster
  • Communicate between instances of our Reliable Service using Reliable Collections
  • Create and manage our first Reliable Actor
  • Use events to communicate between our Reliable Actor and Reliable Service
  • Play with partitioning and replication level
11:00-12:30 - Service Bus hands-on (Radu Pascal) 
  • Create instances for Service Bus Namespace from Azure Portal
  • Use Azure Service Bus Explorer to create and manage a Topic (including filters)
  • Create a sender for our Topic
  • Create a receiver app
  • Explore poisonous messages and dead letter queue feature
  • Play with long running handlers
12:30-14:00 -Azure SQL Database - Everyone's intelligent cloud database (Silviu Niculiță)  
  • Scale database performance on the fly, without app downtime
  • Build multitenant apps with customer isolation and efficiency
  • Work within your preferred development environments
  • Protect and secure your app data
 

Mulțumim sponsorilor pentru susținere!
 
 
ISDC

 
 

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