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

How to check in AngularJS if a service was register or not

There are cases when you need to check in a service or a controller was register in AngularJS.
For example a valid use case is when you have the same implementation running on multiple application. In this case, you may want to intercept the HTTP provider and add a custom step there. This step don’t needs to run on all the application, only in the one where the service exist and register.
A solution for this case would be to have a flag in the configuration that specify this. In the core you would have an IF that would check the value of this flag.
Another solution is to check if a specific service was register in AngularJS or not. If the service was register that you would execute your own logic.
To check if a service was register or not in AngularJS container you need to call the ‘has’ method of ‘inhector’. It will return TRUE if the service was register.
if ($injector.has('httpInterceptorService')) { $httpProvider.interceptors.push('httpInterceptorService&#…

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine:
threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration:

TeamCity.NET 4.51EF 6.0.2VS2013
It seems that there …

Run native .NET application in Docker (.NET Framework 4.6.2)

Scope
The main scope of this post is to see how we can run a legacy application written in .NET Framework in Docker.

Context
First of all, let’s define what is a legacy application in our context. By a legacy application we understand an application that runs .NET Framework 3.5 or higher in a production environment where we don’t have any more the people or documentation that would help us to understand what is happening behind the scene.
In this scenarios, you might want to migrate the current solution from a standard environment to Docker. There are many advantages for such a migration, like:

Continuous DeploymentTestingIsolationSecurity at container levelVersioning ControlEnvironment Standardization
Until now, we didn’t had the possibility to run a .NET application in Docker. With .NET Core, there was support for .NET Core in Docker, but migration from a full .NET framework to .NET Core can be costly and even impossible. Not only because of lack of features, but also because once you…