How can you create an application that has truly global reach, and can scale rapidly to meet sudden massive spikes in demand? Historically, companies had to invest in an infrastructure capable of supporting such an application themselves, and plan for peak demandโwhich often means that much of the c
Developing Multi-tenant Applications for the Cloud on Windows Azure
โ Scribed by Dominic Betts, Alex Homer, Alejandro Jezierski, Masashi Narumoto, Hanzhong Zhang, Bill Hilf
- Publisher
- Microsoft patterns & practices
- Year
- 2013
- Tongue
- English
- Leaves
- 287
- Series
- Microsoft patterns & practices
- Edition
- 3
- Category
- Library
No coin nor oath required. For personal study only.
โฆ Synopsis
How can you create an application that has truly global reach, and can scale rapidly to meet sudden massive spikes in demand? Historically, companies had to invest in an infrastructure capable of supporting such an application themselves, and plan for peak demandโwhich often means that much of the capacity sits idle for much of the time. Typically, only large companies would have the available resources to risk such an enterprise.
The cloud has changed the rules of the game. By making infrastructure available on a โpay as you goโ basis, creating a massively scalable, global application is within the reach of both large and small companies. Yes, by moving applications to the cloud youโre giving up some control and autonomy, but youโre also going to benefit from reduced costs, increased flexibility, and scalable computation and storage.
This guide is the third release of the second volume in a series about Windows Azure. It demonstrates how you can create from scratch a multi-tenant, Software as a Service (SaaS) application to run in the cloud by using the Windows Azure tools and the increasing range of capabilities of Windows Azure.
The guide focuses on both good practice design and the practicalities of implementation for multi-tenant applications, but also contains a wealth of information on factors such as security, scalability, availability, and elasticity that are relevant to all types of cloud hosted applications.
The guide is intended for any architect, developer, or information technology (IT) professional who designs, builds, or operates applications and services that run on or interact with the cloud. Although applications do not need to be based on the Windows operating system to work in Windows Azure, or be written using a .NET language, this guide is written for people who work with Windows based systems. You should be familiar with the .NET Framework, Visual Studio, ASP.NET MVC, and Visual C#.
๐ SIMILAR VOLUMES
This book is the second volume in a planned series about Windows Azure technology platform. Volume 1, Moving Applications to the Cloud on the Windows Azure Platform, provides an introduction to Windows Azure, discusses the cost model and application life cycle management for cloud-based applications
This book is the second volume in a planned series about Windows Azure technology platform. Volume 1, Moving Applications to the Cloud on the Windows Azure Platform, provides an introduction to Windows Azure, discusses the cost model and application life cycle management for cloud-based applications
How do you build and deploy applications to be scalable and have high availability? Along with developing the applications, you must also have an infrastructure that can support them. You may need to scale up or add servers, have redundant hardware, and add logic to the application to handle distrib
How do you build and deploy applications to be scalable and have high availability? Along with developing the applications, you must also have an infrastructure that can support them. You may need to scale up or add servers, have redundant hardware, and add logic to the application to handle distrib
The IT industry has been evolving at a rapid pace; and with the advent of cloud computing the rate of evolution is accelerating significantly. However, most organizations still have a lot of IT assets running in on-premises datacenters.<br />We are in the middle of a transition between running every