Try one of the apps below to open or edit this item. Developing Multi-tenant Applications for the Cloud 3rd Edition.pdf.
for the
Cloud,
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.
Software Architecture and Software Development
Make critical design and technology selection decisions by highlighting the appropriate solution architectures, technologies, and Microsoft products for common scenarios Understand the most important concepts needed for success by explaining the relevant patterns and prescribing the important practices
Hosting a Multi-tenant Application on Windows Azure Selecting a single or a multi-tenant architecture, stability, scalability, SLAs, authentication, ALM, monitoring, customization
Maximizing Availability, Scalability, and Elasticity Geo-location, CDN, asynchronous execution, autoscaling roles
Securing Multi-tenant Applications Protecting sensitive encoding="utf-8"?> ... ... ...
101
102
ch a pter four
This example ServiceDefinition.csdef file does not exactly match the file in the downloadable solution, which uses a different name for the SSL certificate. Remember, you may want to use different SSL certificates when you are testing the application using the local compute emulator. You must make sure that the configuration files reference the correct certificates before you publish the application to Windows Azure. For more information about managing the deployment, see Chapter 3, “Moving to Windows Azure Cloud Services,” in the guide “Moving Applications to the Cloud.” In addition to the two web role projects, the solution also contains a worker role project and a library project named TailSpin.Web.Survey.Shared that contains code shared by the web and worker roles. This shared code includes the model classes and the ... > ...
Pa rtitioning Multi-Tena nt A pplications
... ... ...
This example shows how to configure a default cache that use 30% of the available memory in the Tailspin.Web web role instances. It uses the local storage emulator to store the cache’s runtime state, and you must change this to use a Windows Azure storage account when you deploy the application to Windows Azure. Tailspin used NuGet to add the required assemblies and references to the Tailspin.Web.Survey. Shared project. Configuring the Session State Provider in the TailSpin.Web Application The final changes that Tailspin made were to the Web.config file in the TailSpin.Web project. The following example shows these changes. XML ...
