Skip to main content

Day 1 of TechEd 2012 - Amsterdam

In aceasta saptamana particip la TechEd Europe. 2012 este primul an cand TechEd se tine in Amsterdam. Locatia aleasa este Amsterdam RAI, un centru de conferinte destul de mare. In unele cazuri iti poate lua si 20 de minunte ca sa ajungi de la o sesiune la alta, iar chiar si cu harta in mana de poti pierde pe holuri.

Haideti sa vedem la ce sesiuni am fost azi. Am inceput cu keynote-ul unde ni s-au prezentat ultimele produse in care Microsoft pompeaza resurse la greu, in special Windows 8 si Azure. Dupa acesta introducere am fost la "Meet the Windows Azure". A fost un overview despre noua versiune de Windows Azure si ce aduce nou. Cel mai importat lucru pentru mine din cadrul acestei sesiuni a fost memory cache-ul, care lipsea pana acuma si modul in care se pot atasa partii virtuale la o masina.
A treia prezentare a fost despre Visual Studio 2012. Mi s-a parut cea ma buna sesiune din ziua de azi la care am participat. De ce? A fost singura sesiune la care am invatat lucuri noi si foarte interesante. Am continuat cu "An Overview of Managing Applications, Services & Virtul Machines in Windows Azure", unde nu am apucat deloc sa ma plictisesc. Am continuat cu Windows Azure, a.i. ultima sesiune pe ziua de azi la care am participat a fost "Cloud-Ready Data Services".
Hot tip of the day: Cei de la Nokia au anuntat ca cea mai mare parte din modele cu Windows  Phone 7 o sa suporte si Windows Phone 8 (seria Lumia si se pare si 610). Asa ca putem sa stam linistiti, strategia lor de marketing ne pune intr-un loc sigur.
A fost o zi extrem de interesanta si imi doresc sa vad asa ceva si in Romania. Ne auzim maine seara.

Update: http://mashable.com/2012/06/20/windows-phone-7-8/ Nokia Lumia 900 with Windows Phone 8. 

Comments

  1. Cei de la HTC nu au zis nimic de upgrade-ul la WP 8? :) (nu WP 7.8)

    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