Windows Azure 12/12/11 Announcement | Annonces Windows Azure du 12 décembre 2011

This afternoon, Microsoft announced a number of updates and improvements to Windows Azure that will help developers to more easily access Windows Azure and unlock the value of cloud computing as a development platform. Cet apr%u00e8s-midi, Microsoft a annonc%u00e9 un certain nombre de mises %u00e0 jours et am%u00e9liorations pour Windows Azure qui aideront les d%u00e9veloppeurs %u00e0 acc%u00e9der tirer un meilleur parti de cette plateforme de d%u00e9veloppement cloud.
Additionally, tomorrow night (tuesday 13th 18:00-2:00 Paris Time), senior Microsoft leaders will participate in a broadcast event: Learn Windows Azure to demonstrate how easy it is for developers to get started with Windows Azure and show how to build scalable cloud applications using Visual Studio.  The event will include a number of great hands-on demos as well. De plus, demain soir mardi 13 de 18:00 %u00e0 2:00, quelques VIP de Microsoft vont participer %u00e0 un %u00e9v%u00e9nement en ligne: Learn Windows Azure qui d%u00e9montrera la facilit%u00e9 avec laquelle les d%u00e9veloppeurs peuvent d%u00e9marrer sur Windows Azure et comment construire des applications qui passent %u00e0 l’%u00e9chelle avec Visual Studio. L’%u00e9v%u00e9nement incluera un certain nombre de d%u00e9mos %u00e9galement.
In this release, we really focused on ease of use and creating more value for .NET developers as well as opening up new opportunities for open source developer to take advantage of Windows Azure.  Among the highlights: Dans cette version, on se concentre sur la facilit%u00e9 d’utilisation et la cr%u00e9ation de valeur pour les d%u00e9veloppeurs .NET et l’ouverture de nouvelles opportunit%u00e9s pour les d%u00e9veloppeurs open source avec Windows Azure. Parmi ces nouveaut%u00e9s:

– New and Enhanced Open Source Software Experience-Windows Azure SDK for Node.JS makes Windows Azure a first-class environment for Node.JS developers that support hosting, storage (blobs, tables, queues).

– Nouvelle exp%u00e9rience Open Source. Le SDK Windows Azure pour Node.JS donne une place de premier rang aux d%u00e9veloppeurs Node.JS. Ce SDK fonctionne avec le Web Role, le Worker role, le stockage (blobs, tables, queues).

– A new Hadoop Service Preview for Windows Azure brings Hadoop Big Data capabilities to Windows Azure and enables Hadoop apps to be deployed in hours instead of days.  To gain greater insights on data (structured, semi-structured and unstructured data), Hadoop on Windows Azure will enable customers to analyze data through familiar tools such as Excel and Microsoft BI tools such as Power View and PowerPivot.

– Une version CTP du service Hadoop pour Windows Azure qui apporte des fonctionnalit%u00e9s de Big Data et permet surtout %u00e0 des applications Hadoop d’%u00eatre d%u00e9ploy%u00e9es en quelques heures et non en plusieurs jours. Pour tirer partie des donn%u00e9es (structur%u00e9es, partiellement structur%u00e9es ou non structur%u00e9es), Hadoop sur Windows Azure permettra d’analyser des donn%u00e9es %u00e0 travers des outils familiers comme Excel ou la plateforme BI (dont Power View ou PowerPivot).
– Increased SQL Azure maximum database sizes in SQL Azure (at no additional cost) and a new sharding pattern to simplifies elastic scale-out – une taille maximum de base de donn%u00e9es SQL Azure augment%u00e9e (sans co%u00fbt additionnel) et le sharding pour permettre une mont%u00e9e en charge horizontale

You can find more details on the announcement here.

On trouvera tous les d%u00e9tails dans ce billet.
   
This shows that Windows Azure is not only for .NET code. Windows Azure support for Node.JS is truly done as a Platform as a Service (PaaS). Just try this out by using the demo script in the Windows Azure training kit  and use it yourself (SDK is here). Cela montre que Windows Azure n’est pas que pour du code .NET. Le support de Node.JS dans Windows Azure est vraiment fait sous la forme de PaaS (plateforme en tant que service). Essayez-le en regardant d’abord le document de d%u00e9monstration de ce sc%u00e9nario dans le kit d’apprentissage puis essayez-le vous-m%u00eame (Le SDK est ici).
Node.JS is one the scenarios. Have a look at the new developer center: Node.JS est un des sc%u00e9narios. Allez voir le nouveau centre de d%u00e9veloppement:
You can also find code on the GitHub repository at https://github.com/WindowsAzure, and ask questions on the stackoverflow forums http://stackoverflow.com/search?q=azure. Vous pouvez aussi trouver du code sur GitHub %u00e0 https://github.com/WindowsAzure, et poser des questions sur les forums stackoverflow http://stackoverflow.com/search?q=azure.

Benjamin

Blog Post by: Benjamin GUINEBERTIERE

Ordina behaalt zilver in Microsoft Applicatie integratie

Ordina behaalt zilver in Microsoft Applicatie integratie

Afgelopen week heeft Ordina AIM binnen het Microsoft Partner Model de mooie zilveren status behaald binnen de competentie “Applicatie Integration”. Onder deze competentie vallen onder andere de bekende producten zoals BizTalk en WCF. Mede dankzij effort van Steef-Jan Wiggers en Sjoerd van Lochem is deze eerste mooie stap gemaakt. Steef-Jan ligt de prestatie verder toe:

Het Partner Model bij Microsoft is volledig op de schop gegaan, omdat in feite in heel de wereld en dus ook in Nederland teveel partners de status van “Gold” Partner hadden. Het onderscheid tussen de partners was in zijn geheel niet meer duidelijk. En “Gold” Partner waarin? Je bent Microsoft “Gold” Partner, maar wat betekent dit nu in feite voor mij als klant en waar onderscheid jij als leverancier van Microsoft diensten nu van de rest.

Als je voldoende opbrengsten levert als partner op Microsoft producten en diensten en voldoende gecertificeerde mensen in dienst hebt, dan was je “Gold” partner. Het nieuwe Partner Model van Microsoft is georganiseerd op basis van competentie, waarbij criteria gelden voor:

Referenties
Certificering
Omzet

Op basis van je status op competentie kun je je onderscheiden van andere partners. Er zijn diverse competenties voor virtualisatie, communicatie, desktop, web development, applicatie integratie enzovoort. Op de competentie kun je een “Silver” of “Gold” status behalen.

Als Ordina AIM zijn we trots dat we de “Silver” status hebben kunnen behalen voor “Applicatie Integration”. De “Silver” status betekent dat we als Ordina AIM aan onze klanten kunnen laten zien, dat we voldoende referenties hebben opgebouwd op het gebied van applicatie integratie, voldoende gecertificeerde mensen aan boord hebben en omzet maken door het leveren van diverse diensten. We behoren met deze status op “Applicatie Integratie” tot 5% van alle bedrijven wereldwijd, die dergelijke status hebben op deze competentie.

De “Silver” status is een mooie mijlpaal, die we hebben bereikt. We willen uiteindelijk natuurlijk de status “Gold”. Deze status geeft ons nog meer onderscheidend vermogen ten opzichte van onze concurrenten. Met deze status kunnen we namelijk aantonen dat we wereldwijd tot de beste behoren op het gebied van “Applicatie Integration”. De status toont onze commitment tot Microsoft technologie, die bij deze competentie hoort. Technologie als BizTalk Server, Windows Communication Foundation (WCF) en SQL integratie technologie als Integration Services en SQL Broker. Als Ordina AIM zijn we in staat specifieke, hoogwaardige oplossingen te leveren en de “Gold” status zal uiteindelijk het bewijs richting onze klanten zijn.

Contest at Sandro’s blog: Win an e-copy of Microsoft BizTalk Server 2010 Patterns book

Sandro Pereira has a contest in which you can win an e-copy of Microsoft BizTalk Server 2010 Patterns from Packt Publishing.

Since I love the book as well (got the printed version), I thought I’d try to give the contest some extra attention.

If you would like to win an e-copy, be fast: the contest closes Friday December 16th.

The value of a Diagnostics service

For an integration solution with lots of dependencies, it’s difficult to definitively state that everything is wired up correctly and that all components in the stack are working. A while ago, Michael Stephenson proposed having a diagnostic service in a solution as a quick way of verifying that a given environment was working, end-to-end. Initially I was sceptical, on the grounds that there shouldn’t be any code in a solution which isn’t directly solving a business problem, but having tried it out I’ve been won over.

We now have a dedicated suite of diagnostics services which check a whole range of stuff, including availability of all the downstream services, the in-process and out-of-process caches, and the accessibility of BizTalk file drops. We also include environmental stuff like the version number of the solution, machine name, server date and time, IP addresses etc. And we have a rolled-up service which gives us a green or red status for the solution.

For devs and technical owners of the solution, this gives us a very detailed view of the health of the stack, but we have REST endpoints for the general healthcheck services, and we now use these all over the place:

  • in our automated deployment process, we send an email after an environment had been deployed. That email contains the output of the healthcheck service, so we can tell if a deployment was successful;
  • the REST URLs are published to the team, so testers and service consumers can quickly check if the environment is operational before starting work on a release;
  • we have something like 10 environments which are all catalogued, and the REST URL for the version number service means we’re not manually updating version numbers in the catalogue after a release;
  • we have nightly releases of the integration solution and the downstream services, so we have simple PowerShell script run from a Windows schedule every morning, which checks the output of the REST services and emails the team with the test environment status;
  • calling the diagnostic service warms up the server app pool, and all the app pools of the downstream services, so the scheduled job warms everything up after a recycle.

With this simple stuff in place we’re saving a bunch of time investigating problems which turn out not to be problems in the integration solution, and the offshore test team can quickly see if there are problems with the stack before investing time on tests. Highly recommended.

Contest: Win an e-copy of Microsoft BizTalk Server 2010 Patterns book

Contest: Win an e-copy of Microsoft BizTalk Server 2010 Patterns book

After having raffled, along with Ruth Resende (MVP BizTalk), two e-copies of this book for the BizTalk Portuguese/Brazilian community on the site BizTalk Brasil Is now time, and getting into the Christmas Spirit, to provide two Christmas presents to my readers and for the BizTalk community. I have 2 e-copies of the new book Microsoft […]
Blog Post by: Sandro Pereira

WCF 4.5 WF 4.5 VSNET 2011: Some details

Hi folks, as you may/may not have been aware these are the core corner stone technologies
of the MS Integration Stack.

The teams have been busily plugging away and coming up with the new versions – 4.5
corresponding to .NET 4.5 framework.

Here’s some links that describe what’s new from MS Santa & his elves:

  1. What’s
    New in Windows Communication Foundation 4.5
    1. New Items I found of note are:
      • New Service Transport Default values – keep an eye on these.
      • Improvements from VS.NET 2011 – validation , better intellisence support.
      • Streaming improved – true async (yay!)
      • WebSocket support – through NetHttp(s)Binding
      • Single WSDL file generation with ’?singleWSDL’ (which is pretty handy)
      • Self hosted + II hosted allow you to get to ServiceHost from code
        for dynamic configuration.
      • Binary Encoder supports compression!! – this is generally gzip compression.
      • My personal favourite – UDP support

      >

    2. What’s
      New in Windows Workflow Foundation in .NET 4.5
      1. New Items of note are:
        • New Activites – NoPersistScope (possible previously but we needed to write code)
        • WF Designer improvements – several here, but the ’Outline view’ looks to be easier
          to work with.
        • C# Expressions – where’s the F# ones ??
        • Designer Annotations – add your own comments to keep control of the jungle that is
          built.
        • WF Versioning – use WorkflowIdentity & DefinitionIdentity to define the version. WorkflowServiceHost supports
          multiple versions of the same WF. All pretty cool.
        • WF Designers can still be rehosted – I’ve used that many a place.
        • Contract First Development – ticks the boxes.
      2. WF Rules – still didn’t make the cut. There is a sample for WF4 using
        a custom Activity calling back to WF 3.5 Policy4 it’s called. It
        uses ’interop’ back to WF3.5 and is found here – http://msdn.microsoft.com/en-us/library/dd797584(v=VS.100).aspx
        1. Will have to check out perf in this new land on these rules.

        >

      3. Async CTP – while this didn’t make the ’whats new’ list, it certainly
        does deserve a mention here.
        Over the last year I’ve built some pretty serious F# projects, and F# has the async
        support through and through the language. After over coming the challenge of learning
        it, the Async functionality is absolutely brilliant!!! F# does a great job in being
        able to turn a non-async chunk of code/method/class into an async one with by using
        the keyword async and a !. It’s straight forward
        from that aspect.

        It’s great to see the C# & VB.NETs being able to use the same fundamentals (albeit
        not as slick IMO ).
        – see a previous POST – http://blogs.breezetraining.com.au/mickb/2011/04/26/EasierAsyncProgrammingComingToCVBSoon.aspx

        As developers we sit here and say – what do I need this for? My code
        runs fine as it.and yes for the most part of what we do on our machine it does. This
        technology really comes into it’s own when you want consistent throughput from a solution
        with 1 person or 10000 concurrent people using it. That’s the difference.

        To use it:

        1. Get VSNET 2011 (as it requires a new compiler)
        2. Use ASYNC CTP (refresh3) with VSNET2010 SP1
      4. Check it out from here – http://msdn.microsoft.com/en-us/vstudio/gg316360
      5. >

        Blog Post by: Mick Badran