Skip to main content

Day 4 of TechEd 2012 - Amsterdam

Astazi a fost ultima zi a TechEd Europe 2012. Ca orice ultima zi a trecut extrem de repede dar a fost plina de continut de specialitate. Haideti sa vedem la ce sesiuni am fost astazi.
Am inceput ziua asa cum se cuvine, cu o sesiune de async calls pentru .NET 4.5 - "Async made simple in Windows 8, with C# and VB". Pot sa va spun ca am savurat aceasta prezentare, nu din cauza ca era vorba despre async, ci din cauza ca odata la 2-3 minute aflai ceva noi. Desi pana acuma am folosit async, am aflat destul de multe lucruri noi in cadrul acestei sesiuni pe care nu le stiam pana acuma.
Urmatoarea pe lista a fost "Achieving Enterprise Integration Patters with Windows Azure Service Bus". A fost o sesiune la fel de interesata ca si prima, iar la cum se anunta lucrurile Service Bus-ul din Azure devine din ce in ce mai serios. Nu mai este o jucarie.
A treia sesiune din ziua de azi a fost "Building High Performing Parallel Application Services on Windows Azure". Aveam alte asteptari de la aceasta sesiune, a fost destul de seaca, iar continutul nu a fost la cea ce ma asteptam din pacate.
TechEd-ul l-am terminat cu "Developing High Performing Parallel Application Services on Windows Azure". Se pot face lucruri foarte frumoase pe Windows Azure, mai ales cand vorbim de simulari si de analize date, sper sa am ocazie sa lucrez vreodata la un simulator care isi face partea computationala in cloud.
Primele doua prezentari din acesta zi au fost cireara de pe tort de la tot TechEd-ul pentru mine. Doar pentru aceste doua prezentari merita un drum in Amsterdam.
Hot tip of the day: In aceata zi este despre Service Bus si SharePoint. Se zvoneste prin Amsterdam ca urmatoarea versiune de SharePoint o sa foloseasca pe partea de workflow (in zona de session state) Service Bus. O sa revin cu un post pe aceasta tema cat de curand.
Si bonus, pentru cei care au Windows Phone 7+, daca tineti timp de 5 secunde butonul de lock cand acesta este blocat, camera video se porneste automat.
La revedere Amsterdam, la revedere TechEd Europe 2012. Ne vedem anul viitor.

Comments

  1. Nice :)
    Cat despre WP7, probabil depinde de producator - daca apas 5s butonul de lock face shutdown la mine - pentru camera video e suficient sa apas mai mult butonul dedicat din dreapta si porneste, chiar daca e in lock mode..

    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