Skip to main content

Google App Engine vs Microsoft Azure

Side Stepping on my OSGi trail, I saw a few articles on the new Azure platform for Cloud computing from Microsoft! People claiming it to be up agains Amazon EC2 and Google App Engine.

Come on.. Having never used it, I cant speak for EC2 but; App Engine and Azure? Where is the comparision.

By Choosing Azure, I am basically TIED to Windows all the way! Just look at the long list of Auzure SDK Requirements:

  • Supported Operating Systems: Windows Server 2008 Enterprise; Windows Server 2008 Standard; Windows Vista Business; Windows Vista Business 64-bit edition; Windows Vista Home Premium; Windows Vista Home Premium 64-bit edition; Windows Vista Ultimate; Windows Vista Ultimate 64-bit edition
  •  Required Software
    •  Windows Vista SP1 (when installing on Windows Vista)
    •  .NET Framework 3.5 SP1
    •  IIS 7.0 (with ASP.NET and WCF HTTP Activation)
    •  Microsoft SQL Server Express 2005 or Microsoft SQL Server Express 2008
    •  Windows PowerShell (optional)

On the other hand, App engine can live on Windoze, Linux or Mac. Other requirements: Python - available in any OS. THATS it. They even have plans to get Java, Perl and other languages to be supported. The only thing we get tied to is Google BigTable DataStore.

It looks like the age old race with httpd for IIS. Déjà vu.

Popular posts from this blog

Appcache manifest file issues/caveats

Application cache (appcache) is a powerful feature in HTML5. However, it does come with baggage. Many (see links below) advocated ferociously against it due to tricky issues it comes with. For someone who is just testing waters, these issues may throw them off grid. Knowing them before hand helps reduce some unpredictable effects.

Being a Vegetarian

I am a Proud Vegetarian. I don't eat Meat or Eggs. People say its hard here in US to be one. I beg to differ. The mere fact that I am hail and healthy these 4 years is a definitive proof. Apart from being bullied and trash talked by The Meat-Eaters, There is really nothing that makes this choice of mine any more than a debatable issue at a lunch or dinner. Other things aside, I am writing this blog having watched a PETA Video. Before you click on the play button, I ask you - If you are a vegetarian : Dont watch it. If you are not : Dare to watch it till the end. If you think going veg is just a fashion, think again . Even if you just want to do it for Fashion . Do it. Go Vegetarian. And Feel better asking the waiter for a Vegetarian Entrée in your next lunch.

classpath*: making your Modular Spring Resources

Spring gives multiple options to load XML resources for building contexts. the reference documentation does explain this feature quite well. However, I am taking my shot at explaining the different practical scenarios ( by order of growing modularisation) For Example, A simplest Spring based web Context Loader can be configured with resources like this <context-param> <param-name>contextConfigLocation</param-name> <param-value>applicationContext.xml</param-value> </context-param> <listener> <listener-class>org.springframework.web.context.ContextLoaderListener</listener-class> </listener> You just need to put applicationContext.xml in WEB-INF/ folder of your webapp. However, Typically an application is n-tiered. You can also have multiple files setup and in relative paths. like <param-value> context-files/applicationContext.xml context-files/dao.xml context-files/service.xml </param-value>