Skip to main content

Day 2 of TechEd 2012 - Amsterdam

Si iata ca a trecut si a doua zi din TechEd Europe 2012. Daca ziua de ieri a fost dedicata cloud-ului, atat public cat si privat, ziua de azi a stat sub semnul Windows 8 impreuna cu cloud. In comparatie cu ziua de ieri, sesiunile din aceasta zi au fost mult mai interesante, s-a trecut usor de la generalitati la lucruri la complexe.
Ziua a inceput destul de devreme, dar in forta. Antoine Leblond a deschis ziua a doua cu un keynote despre Windows 8. Au fost prezentate atat functionalitatile de baza cat si cele pentru mediul enterprise. De exempl cum poti sa iti iei calculatorul de la servici pe stick si sa il folosesti de acasa, fara a trebui sa instalezi orice alt produs sau sa iti pui probleme de securitate.
Dupa aceasta sesiune am participat la sesiune lui NIck Harris despre cum sa contruiesti o aplicatie pentru Windows 8 care sa foloseasca pe partea de backend Windows Azure. A fost o prezentare pe gustul oricarui dezvoltatori. Aplicatia a fost scrisa de la 0 in cele 75 de minute.
Cum nu aveam inca o idee foarte bine formata despre Private Cloud, am decis sa participa la sesiunea "Private Cloud Principles, Concepts and Pattern", sustinuta de Tom Shinder. A fost o prezentare extrem de utila, cu foarte mult continut folositor. Cea mai importanta concluzie dupa aceasta prezentare a fost ca Private Cloud nu inseamna o fabrica de servere on-premise, poate sa fie si Windows Azure sau o combinatie intrece cele doua. Private Cloud reprezinta un mediu privat unde doar o anumita are acces si se poate folosi de resurse.
Vishal Joshi a vorbit despre "App Deployment Options for Windows Azure". Ne-a fost prezentate modalitatile prin care se poate face deploy la o aplicatie in Windows Azure. De la Visual Studio si TFS, pana la FTP si Git.
In urma keynote-ului de azi dimineata m-a decis sa particip la sesiune lui Brad McCabe - "Windows 8 - Overview for the enterprise, Enabling FlexibleWorkstyles". Eram curios sa vad ce aduce nou acest sistem de operare pentru cei din enterprise. Tot ce pot spune este ca IT-ul o sa fie mult mai fericit de acuma incolo.
Ziua am terminat-o in forta cu Steve Marx care a vorbit despre software as a service solutions in Windows Azure. Ca si continut mi s-a parut cea mai reusita prezentare la care am participat astazi.
Hot tip of the day: Daca am aloca cate 10MB la fiecare chinez, Windows Azure ar avea inca spatiu de stocare available. Ce inseamnata asta? Hai sa vedem:
1339724852 persons x 10 MB = 13397248520 MB = 13083250 GB = 12776 Tera = 12.5 PB (Petabyte)
Frumos spatiu de stocare, care cu fiecare secunda continua sa creasca.
Ne auzim maine seara? Va ofer posibilitatea ca sa imi propuneti pentru ziua de vineri la ce sesiuni sa particip. Astept propuneri de la voi.

Comments

  1. Din cate stiu Azure storage avea din cate stiu injur de 100 PetaBytes in productie..

    ReplyDelete
    Replies
    1. Valoarea data (12.5) se refera la cat spatiu este available in momentul de fata.

      Delete
    2. Am fost azi la standul celor de la Azure ca sa ii intreb daca ii 100PB sau 12PB. Din pacate nu am primit inca un raspuns, dar au zis ca o sa ma contacteze pe email.
      Nici macar ei nu stiu cat de mare ii :-)

      Delete
  2. Stiu ei foarte bine :), dar sunt informatii interne care nu sunt chiar publice: eu valoarea am gasit-o intr-un research paper de la MS care explica detaliile interne Azure storage: http://sigops.org/sosp/sosp11/current/2011-Cascais/printable/11-calder.pdf
    unde ziceau:
    "We currently have 70 petabytes of raw storage in production and are in the process of provisioning a few hundred more petabytes of raw storage based on customer demand for 2012"

    Desigur, cifra asta se refera la capacitatea totala/fizica, inclusiv ce foloseste MS pentru serviciile proprii gen Bing ..

    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