Book Image

Applied Architecture Patterns on the Microsoft Platform

Book Image

Applied Architecture Patterns on the Microsoft Platform

Overview of this book

Every day, architects and developers are asked to solve specific business problems in the most efficient way possible using a broad range of technologies. Packed with real-world examples of how to use the latest Microsoft technologies, this book tackles over a dozen specific use case patterns and provides an applied implementation with supporting code downloads for every chapter. In this book, we guide you through thirteen architectural patterns and provide detailed code samples for the following technologies: Windows Server AppFabric, Windows Azure Platform AppFabric, SQL Server (including Integration Services, Service Broker, and StreamInsight), BizTalk Server, Windows Communication Foundation (WCF), and Windows Workflow Foundation (WF). This book brings together – and simplifies – the information and methodology you need to make the right architectural decisions and use a broad range of the Microsoft platform to meet your requirements. Throughout the book, we will follow a consistent architectural decision framework which considers key business, organizational, and technology factors. The book is broken up into four sections. First, we define the techniques and methodologies used to make architectural decisions throughout the book. In Part I, we provide a set of primers designed to get you up to speed with each of the technologies demonstrated in the book. Part II looks at messaging patterns and includes use cases which highlight content-based routing, workflow, publish/subscribe, and distributed messaging. Part III digs into data processing patterns and looks at bulk data processing, complex events, multi-master synchronization, and more. Finally, Part IV covers performance-related patterns including low latency, failover to the cloud, and reference data caching.
Table of Contents (26 chapters)
Applied Architecture Patterns on the Microsoft Platform
Credits
Foreword
About the Authors
About the Reviewer
Preface

Chapter 16. Rapid Flexible Scalability

How often have you looked at the logs that are monitoring a system's usage and seen minimal use of memory, CPU, or other system resources? Servers are built to handle anticipated peak loads. Normal practice and the natural tendency to anticipate the worst and/or cover your behind usually mean that the highest peaks that a server can handle are almost never encountered. This is expensive, both in terms of capital costs for hardware and licenses and operational costs such as electricity, cooling, floor and rack space costs, support staff and other incidental costs. It also imposes significant burdens on the operational staff supporting the machines. The more machines one uses, the more likely it is that one of them will break. In keeping with Murphy's Law, this break will, of course, occur at 4:55 PM on the Friday before a holiday weekend.

The solutions associated with cloud computing have been around for some time but have typically been seen as immature...