|Number of votes:||6|
“EPiServer for Microsoft's cloud Azure , has finally received a launch date. It's April 1st (no joke) that EMVP Alexander Haneng / EPiNova and Daniel Berg / Sogeti 's persistent and extensive project sees the light. Large parts of EPiServer's core should have been rewritten to succeed in being scalable and adaptable for Azure.”
The quote is from the MKSE.com “Sweden's by far the largest site for people who work with or are interested in CMS / WCM / ECM.”
The article continues with “MKSE.com have previously written about cloud ambitions. Even EPiServer itself has managed to adapt and rewrite version 6 with Microsoft's requirements to serve as a Web-based cloud service. Despite several attempts. See eg the articles from 2010 and 2011.”
Although I am flattered that MKSE thinks that I managed to get EPiServer CMS 6 running on Azure (and that EPiServer themselves failed after several attempts), is untrue. I might be an EMVP now, but EPiServer doesn’t let me play with the core (at least not yet, wink, wink). However that Daniel Berg could get EPiServer up on Azure in no time would not surprise me (he has even done a proof of concept for an EPiServer meetup in Stockholm).
And I also want to reassure my boss at Making Waves that I have not quit and start working for EPiNova. (Sorry EPiNova).
Well it had to be Mr. EPiServer Oracle himself, Magnus Rahl (
Making Waves, Sogeti).
On March 1st. he tweeted:
Exactly a month from March 1st. would be Aprils 1st. Also the “EPiSkynet” would indicate a joke to most
March 2nd. MKSE picks up the “story” and writes the article about EPiServer and Azure.
Frederik Vig (
Making Waves, Geta) links to the article:
Soon the “tweetsophere” answers using the hash tag #episkynet:
And my favorite:
The EPiBorg has spoken.
(This was just some of the tweets with the #episkynet hash tag. For the rest (and new tweets) see #episkynet at Twitter)
Posted by Alexander Haneng