How can a company's applications be scalable and have high availability? To achieve this, along with developing the applications, you must also have an infrastructure that can support them. For example, you may need to add servers or increase the capacities of existing ones, have redundant hardware, add logic to the application to handle distributed computing, and add logic for failovers. You have to do this even if an application is in high demand for only short periods of time. Life becomes even more complicated (and expensive) when you start to consider issues such as network latency and security boundaries. The cloud offers a solution to this dilemma. The cloud is made up of interconnected servers located in various data centers. However, you see what appears to be a centralized location that someone else hosts and manages. By shifting the responsibility of maintaining an infrastructure to someone else, you're free to concentrate on what matters most: the application. If the cloud has data centers in different geographical areas, you can move your content closer to the people who are using it most. If an application is heavily used in Asia, have an instance running in a data center located there. This kind of flexibility may not be available to you if you have to own all the hardware. Another advantage to the cloud is that it's a pay as you go proposition. If you don't need it, you don't have to pay for it. When demand is high, you can scale up, and when demand is low, you can scale back. 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. The Windows Azure Architecture Guide shows you how to do this.

Moving Applications to the Cloud on the Microsoft Azure™ Platform (Patterns & Practices)

Computers & Technology

Betts, Dominic

Dunn, Ryan

Woloski, Matias

Pace, Eugenio

Densmore, Scott

Narumoto, Masashi

Networking & Cloud Computing

Microsoft Press

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, and describes how to migrate an existing ASP.NET application to the cloud. This book demonstrates how you can create from scratch a multi-tenant, Software as a Service (SaaS) application to run in the cloud by using the latest versions of the Windows Azure tools and the latest features of the Windows Azure platform. The book 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 Microsoft Windows® operating system to work in Windows Azure, this book is written for people who work with Windows-based systems. You should be familiar with the Microsoft .NET Framework, Microsoft Visual Studio® development system, ASP.NET MVC, and Microsoft Visual C#® development tool.

Developing Applications for the Cloud on the Windows Azure Platform

Programming

Microsoft Pr

This guide describes a scenario around a fictitious company named Tailspin that has decided to include Windows Phone 7 as a client device for their existing cloud-based application. Their Windows Azure-based application named Surveys is described in detail in a previous book in this series, Developing Applications for the Cloud. 
 After reading this book, you will be familiar with how to design and implement applications for Windows Phone 7 that take advantage of remote services to obtain and upload data while providing a great user experience on the device.

Windows® Phone 7 Developer Guide: Building connected mobile applications with Microsoft Silverlight®

Homer, Alex

Boerr, Federico

Salazar, Jose Gallardo

This guide follows a Splunk software engineering team on a journey to build solutions with partners, focusing on the real world use cases to showcase various technologies of the Splunk Developer Platform. Like a documentary, it captures our story from envisioning and user experience prototyping to development, packaging and multiple production deployments. It includes the diverse perspectives of developers and testers, administrators and product owners, security experts and release engineers. As on any real journey, we make mistakes, have arguments, and change our minds along the way. So in addition to showing you how best to do things, we highlight the pitfalls and issues that we encounter, and the solutions we find. The key element of this guidance, of course, is the code. We’ve made the code repos open, and recommend you study the source code of the reference apps and the associated tests. In fact, you can see and replay the code in motion, as it was developed. We encourage you to reuse and learn from it.

Building Splunk Solutions: Splunk Developer Guide (Splunk Developer Guides)

Melnik, Grigori

Foster, David

Jiang, Liying

CreateSpace Independent Publishing Platform

This guide follows a Splunk software engineering team on a journey to build solutions with partners, focusing on the real world use cases to showcase various technologies of the Splunk Developer Platform. Like a documentary, it captures our story from envisioning and user experience prototyping to development, packaging and multiple production deployments. It includes the diverse perspectives of developers and testers, administrators and product owners, security experts and release engineers. As on any real journey, we make mistakes, have arguments, and change our minds along the way. So in addition to showing you how best to do things, we highlight the pitfalls and issues that we encounter, and the solutions we find. The key element of this guidance, of course, is the code. We’ve made the code repos open, and recommend you study the source code of the reference apps and the associated tests. In fact, you can see and replay the code in motion, as it was developed. We encourage you to reuse and learn from it. The second edition is expanded with 10 new chapters, including 3 new ones in the Journey covering OAuth, alerting and high performance HTTP Event Collector. Additionally we include a new section - the Essentials where we've generalized the lessons learned from this Journey and other development projects into fundamental patterns and practices. We still cover the full spectrum of application development from getting data into Splunk Enterprise to packaging and distributing your app. Each topic combines design and implementation guidelines in a way that supports an iterative development process. These guidelines cover not only Splunk Enterprise operational and programming concepts that the application deals with directly, but also consider performance, quality, and maintenance issues in recommending particular approaches.

Building Splunk Solutions (Second edition): Splunk Developer Guide

Tevenan, Matthew

Schutz, Brian

Computer Science

This guide is focused on building highly scalable, highly available, and maintainable applications with the Command &amp; Query Responsibility Segregation and the Event Sourcing architectural patterns. It presents a learning journey, not definitive guidance. It describes the experiences of a development team with no prior CQRS proficiency in building, deploying (to Windows Azure), and maintaining a sample real-world, complex, enterprise system to showcase various CQRS and ES concepts, challenges, and techniques. The development team did not work in isolation; we actively sought input from industry experts and from a wide group of advisors to ensure that the guidance is both detailed and practical. The CQRS pattern and event sourcing are not mere simplistic solutions to the problems associated with large-scale, distributed systems. By providing you with both a working application and written guidance, we expect you’ll be well prepared to embark on your own CQRS journey.

Exploring CQRS and Event Sourcing: A journey into high scalability, availability, and maintainability with Windows Azure (Microsoft patterns & practices)

Subramanian, Mani

Dominguez, Julian

Simonazzi, Fernando

Microsoft patterns & practices

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#.

Developing Multi-tenant Applications for the Cloud on Windows Azure (Microsoft patterns & practices)

Zhang, Hanzhong

Jezierski, Alejandro

Over the years software systems have evolutionarily become more and more complex. One of the techniques for dealing with this inherent complexity of software systems is dependency injection – a design pattern that allows the removal of hard-coded dependencies and makes it possible to assemble a service by changing dependencies easily, whether at run-time or compile-time. It promotes code reuse and loosely-coupled design which leads to more easily maintainable and flexible code. The guide you are holding in your hands is a primer on using dependency injection with Unity – a lightweight extensible dependency injection container built by the Microsoft patterns &amp; practices team. It covers various styles of dependency injection and also additional capabilities of Unity container, such as object lifetime management, interception, and registration by convention. It also discusses the advanced topics of enhancing Unity with your custom extensions. The guide contains plenty of trade-off discussions and tips and tricks for managing your application cross-cutting concerns and making the most out of both dependency injection and Unity. These are accompanied by a real world example that will help you master the techniques. Keep in mind that Unity can be used in a wide range of application types such as desktop, web, services, and cloud. We encourage you to experiment with the sample code and think beyond the scenarios discussed in the guide. In addition, the guide includes the Tales from the Trenches – a collection of case studies that offer a different perspective through the eyes of developers working on the real world projects and sharing their experiences. These chapters make clear the range of scenarios in which you can use Unity, and also highlight its ease of use and flexibility. Whether you are a seasoned developer or just starting your development journey, we hope this guide will be worth your time studying it. We hope you discover that Unity container adds significant benefits to your applications and helps you to achieve the goals of maintainability, testability, flexibility, and extensibility in your own projects.

Dependency Injection with Unity (Microsoft patterns & practices)

See the best price to sell, buy, or rent books by Betts, Dominic. BookScouter helps to compare book prices from 25+ online bookstores and 30+ buyback vendors with a single search.

Books by Betts, Dominic