Hello Folks ,
My this post will give you a very brief overview of Windows azure and its working so here is the post !!!
The Windows Azure Compute service can run many different kinds of applications. A primary goal of this platform, however, is to support applications that have a very large number of simultaneous users. (Infact, Microsoft has said that it will build its own SaaS applications on Windows Azure, which sets the bar high.) Reaching this goal by scaling up—running on bigger and bigger machines—isn’t possible. Instead,
Windows Azure is designed to support applications that scale out, running multiple copies of the same code across many commodity servers.
To allow this, a Windows Azure application can have multiple instances, each executing in its own virtual machine (VM). These VMs run 64-bit Windows Server 2008 i.e Windows Server 2008 R2, and they’re provided by a hypervisor (based on Hyper-V) that’s been modified for use in Microsoft’s cloud. To run an application, a developer accesses the Windows Azure portal through the Web browser, signing in with a Windows Live ID. He/She then chooses
whether to create a hosting account for running applications, a storage account for storing data, or both.Once the developer has a hosting account, He/she can upload her application, specifying how many instances the application needs. Windows Azure then creates the necessary VMs and runs the application.
It’s important to note that a developer can’t supply there own VM image for Windows Azure to run. Instead,the platform itself provides and maintains its own copy of Windows. Developers focus solely on creating applications that run on Windows Azure.
In the initial incarnation of Windows Azure, known as the Community Technology Preview (CTP), two different instance types are available for developers to use: Web role instances and Worker role instances.For getting useful information on Web and worker role please look at my last post.
That's all now for this post hope you are enjoying my post .For any queries kindly contact me.
Jayesh Maduskar
Jayesh.Maduskar@msptechrep.com
Microsoft Student Partner
Sunday, March 27, 2011
Monday, March 21, 2011
Play with Windows Azure Web & Worker Role!!!!!!
Hello Guys....In this post I am going to tell you some cool facts about the web & worker role in Windows Azure.
This roles plays a very major part in the scalability of your application on Windows Azure cloud platform.The reason behind the simplest architecture of windows azure is asynchronous web and worker role. Load balancer is the another key term used in this platform which basically distributes the incoming traffic.Queues which are kinda storage space which are responsible for communication between the web roles and worker roles.The diagram below will give you a clear idea of the terms that were used in the post till now.
Now I am going to concentrate my view on the Web and worker roles so stay tuned to my blog.
Web Role The web role communicates with the outside world through internet.It is the client facing part for our cloud application.There may be a interface associated with this role.
Worker Role The worker role typically plays its role behind the scene.The worker role is basically a code which performs some task .This task may involove writing data to the storage ,carrying out some long running computation.
The Web and Worker roles communicates with one another through "Queues".A queue is the data structure which basically works on FIFO structure which allow us to pass messages back and forth b/w different roles in our application.
I hope I made it bit clear between the web & worker roles the key terms yes the key terms in Windows Azure.You should be very clear with the web and worker roles for understanding the working of Windows Azure platform.
Thanks....Stay tuned to my blog for upcoming post on Development of Cloud Application.
Jayesh Maduskar
Microsoft Student Partner
jayesh.maduskar@msptechrep.com
This roles plays a very major part in the scalability of your application on Windows Azure cloud platform.The reason behind the simplest architecture of windows azure is asynchronous web and worker role. Load balancer is the another key term used in this platform which basically distributes the incoming traffic.Queues which are kinda storage space which are responsible for communication between the web roles and worker roles.The diagram below will give you a clear idea of the terms that were used in the post till now.
Now I am going to concentrate my view on the Web and worker roles so stay tuned to my blog.
Web Role The web role communicates with the outside world through internet.It is the client facing part for our cloud application.There may be a interface associated with this role.
Worker Role The worker role typically plays its role behind the scene.The worker role is basically a code which performs some task .This task may involove writing data to the storage ,carrying out some long running computation.
The Web and Worker roles communicates with one another through "Queues".A queue is the data structure which basically works on FIFO structure which allow us to pass messages back and forth b/w different roles in our application.
I hope I made it bit clear between the web & worker roles the key terms yes the key terms in Windows Azure.You should be very clear with the web and worker roles for understanding the working of Windows Azure platform.
Thanks....Stay tuned to my blog for upcoming post on Development of Cloud Application.
Jayesh Maduskar
Microsoft Student Partner
jayesh.maduskar@msptechrep.com
Tuesday, March 1, 2011
Windows Azure caching Service
Hello Fellas ,Up with my new post on caching service of Windows Azure.You might be thinking that what this cache is doing in between a client and server interaction when we don't have any control over the server as our application is hosted on distributed environment and someone else is taking care of its flow right ?? So just be with me I will show you how this caching concept is added on the Windows Azure Platform providing an unbelievable performance and decreasing the load on data centers.
The caching provides a distributed,in-memory,application cache service for Windows Azure platform and SQL Azure applications resulting in decrease on the databse as well as server interaction and communication.These capabilities are provided as a service on Windows Azure platform.The diagram below is showing a very clear picture of how caching works on Azure platform.
You can add the caching service for your ASP.NET application just by doing minor configuration without changing any application code just few simple lines of code will add the service for your application .The benefits of Caching on Windows Azure are as follows:
* Highly scalable caching solution with low latency and high throughput.
* Provided entirely as a service - no installation or management of instances required.
* Flexible management - dynamically increase/decrease cache size as needed.
* Integrates easily with existing ASP.NET web applications.
The features of Caching for Azure platform are:
* Pre-built ASP.NET providers for session state and page output caching, enabling acceleration of web applications without having to modify application code.
* Caches any managed object - no object size limits, no serialization costs for local caching.
* Easily integrates into existing applications.
* Consistent development model across both Windows Azure AppFabric and Windows Server AppFabric.
* Secured access and authorization provided by the Access Control service.
* Additional features on roadmap: high-availability, configurable regions, notifications, and more.
That's all about the caching feature Stay tuned to my blog for a very important post on Windows Azure application development point to point :)
For any queries don't hesitate to contact me
Jayesh Maduskar
Microsoft Student Partner|Adobe Student Reps
jayesh.maduskar@msptechrep.com
The caching provides a distributed,in-memory,application cache service for Windows Azure platform and SQL Azure applications resulting in decrease on the databse as well as server interaction and communication.These capabilities are provided as a service on Windows Azure platform.The diagram below is showing a very clear picture of how caching works on Azure platform.
You can add the caching service for your ASP.NET application just by doing minor configuration without changing any application code just few simple lines of code will add the service for your application .The benefits of Caching on Windows Azure are as follows:
* Highly scalable caching solution with low latency and high throughput.
* Provided entirely as a service - no installation or management of instances required.
* Flexible management - dynamically increase/decrease cache size as needed.
* Integrates easily with existing ASP.NET web applications.
The features of Caching for Azure platform are:
* Pre-built ASP.NET providers for session state and page output caching, enabling acceleration of web applications without having to modify application code.
* Caches any managed object - no object size limits, no serialization costs for local caching.
* Easily integrates into existing applications.
* Consistent development model across both Windows Azure AppFabric and Windows Server AppFabric.
* Secured access and authorization provided by the Access Control service.
* Additional features on roadmap: high-availability, configurable regions, notifications, and more.
That's all about the caching feature Stay tuned to my blog for a very important post on Windows Azure application development point to point :)
For any queries don't hesitate to contact me
Jayesh Maduskar
Microsoft Student Partner|Adobe Student Reps
jayesh.maduskar@msptechrep.com
Subscribe to:
Posts (Atom)