Let's rokk! [Tudor Cret's blog]

June 14, 2011

10 reasons to use Azure for your cloud apps

Filed under: Windows Azure — Tudor Cret @ 11:09 am
Tags: , ,

1. Familiarity of Windows

Based on Windows you can write .NET apps using C#/VB/C++ and ASP.NET/MVC/Silverlight.

Easy to migrate existing Windows applications.

2. 64-bit Windows Virtual Machines

Each instance of the app running in its own VM on the 64-bit Windows Server 2008 operating system. The hypervisor on which they run is designed specifically for the cloud. You don’t have to supply your own VMs or deal with managing and maintaining the OS because apps are developed using Web role instances or worker role instances that run in their own VMs

3. Azure SDK

You can run locally (on your PC) when developing and debugging an application and then move it to the cloud.

4. Scalability and flexibility

Using Azure, you can easily create applications that run reliably and scale from 10 to 10 thousand or even 10 million users — without any additional coding. Azure Storage provides scalable, secure, performance-efficient storage services in the cloud.

5. Cost benefits and pricing model

No costs for building and/or expanding on-premises resources, pay as you go model.

6. Data Center in the cloud

Relational database engine in the cloud offered by SQL Azure.You get high availability and reliability with redundant copies of your data and automatic failover.

7. Support resources

Because Azure uses the same familiar tools and technologies as other Windows platforms, you can take advantage of the well-established support structure within Microsoft and company-provided resources. Strong communities and world wide forums.

8. Interoperability

You can develop hybrid applications that allow your on-premises applications to use cloud services, such as the cloud database and storage services. Communications services work between on-premises applications and the cloud, as well as mobile devices (HTTP,XML,SOAP,REST). SDKs for Java,PHP,Ruby.

9. Security

Windows Azure AppFabric provides a powerful mechanism to secure your application and your communications to the app.

10. Something for everyone

Windows Azure can benefit hosting providers, ISVs, systems integrators, and custom software developers. Hosting providers can expand their services to areas where they don’t have existing infrastructure and add new services without more infrastructure investment. ISVs can use Azure to create, deploy, and manage Web apps and SaaS without large capital expenditures, and they can scale those applications more quickly and cost effectively. Systems integrators can take advantage of Azure’s ability to work with existing on-premise infrastructures. Custom software developers can create software solutions for customers who can’t afford the costs of in-house development, including hardware costs, and they can deliver their applications to customers as services without building and maintaining an expensive data center.


Azure Named Fastest Cloud Service

Filed under: Windows Azure — Tudor Cret @ 10:34 am
Tags: , ,

According to tests by Compuware’s CloudSleuth service Azure was named the fastest cloud service.

In a comparative measure of cloud service providers, Microsoft’s Windows Azure has come out ahead. Azure offered the fastest response times to end users for a standard e-commerce application. But the amount of time that separated the top five public cloud vendors was minuscule.

These are first results I know of that try to show the ability of various providers to deliver a workload result. The same application was placed in each vendor’s cloud, then banged on by thousands of automated users over the course of 11 months.” The complete ranking board:

  1. Windows Azure
  2. GoGrid
  3. Amazon EC2
  4. Rackspace

The test involved the ability to deliver a Web page filled with catalog-type information consisting of many small images and text details, followed by a second page consisting of a large image and labels. The top five were all within 0.8 second of each other.

The test application is designed to require a multi-step transaction that’s being requested by users from a variety of locations around the world. CloudSleuth launches queries to the application from an agent placed on 150,000 user computers.

The response times were:

  1. Windows Azure (data center outside Chicago) – 10.142 seconds
  2. GoGrid – 10.468 seconds
  3. Amazon EC2 Northen Virginia – 10.942 seconds
  4. Rackspace  – 10.999 seconds
  5. Amazon EC2 West (Washington State) – 11.838 seconds
  6. OpSource, Calif. – 12.440 seconds
  7. GoGrid West – 12.604 seconds
  8. Terremark – 12.971 seconds
  9. CloudSigma – 18.079 seconds
  10. Amazon EC2 Europe/Ireland – 18.161 seconds
  11. Windows Azure for Southeast Asia – 27.534 seconds
  12. Amazon EC2 Asia/Pacific Singapore – 30.965 seconds

The response times include all the latencies of the last mile of service as the message moves off the Internet backbone and onto a local network segment. The response times reflect what end users are likely to see "at the edge of the network”.

The results listed:

  • are averages for the month of December, when traffic increased at many providers. Results for October and November were slightly lower, between 9 and 10 seconds.
  • are an average for each vendor, a composite response time compiled from 90,000 browser calls a month to the target application placed in each service provider’s cloud.

The original article is available on the informationweek.com’s page here.

Create a free website or blog at WordPress.com.