Book Image

Distributed .NET with Microsoft Orleans

By : Bhupesh Guptha Muthiyalu, Suneel Kumar Kunani
Book Image

Distributed .NET with Microsoft Orleans

By: Bhupesh Guptha Muthiyalu, Suneel Kumar Kunani

Overview of this book

Building distributed applications in this modern era can be a tedious task as customers expect high availability, high performance, and improved resilience. With the help of this book, you'll discover how you can harness the power of Microsoft Orleans to build impressive distributed applications. Distributed .NET with Microsoft Orleans will demonstrate how to leverage Orleans to build highly scalable distributed applications step by step in the least possible time and with minimum effort. You'll explore some of the key concepts of Microsoft Orleans, including the Orleans programming model, runtime, virtual actors, hosting, and deployment. As you advance, you'll become well-versed with important Orleans assets such as grains, silos, timers, and persistence. Throughout the book, you'll create a distributed application by adding key components to the application as you progress through each chapter and explore them in detail. By the end of this book, you'll have developed the confidence and skills required to build distributed applications using Microsoft Orleans and deploy them in Microsoft Azure.
Table of Contents (17 chapters)
1
Section 1 - Distributed Applications Architecture
4
Section 2 - Working with Microsoft Orleans
10
Section 3 - Building Patterns in Orleans
13
Section 4 - Hosting and Deploying Orleans Applications to Azure

Understanding cloud design patterns

Patterns are low-level specific implementation guidelines that are proven reusable solutions for recurring problems. Each of the following patterns can be implemented in Microsoft Azure to build reliable, scalable, and secure distributed applications.

The gateway aggregation pattern

The gateway aggregation pattern aggregates multiple client requests targeting multiple backend services in a single client request, dispatches the requests to various backend services, then aggregates the responses received from all backend services into one response and sends it back to the client.

Usage

This pattern is very useful to reduce the chattiness between the client and multiple backend services, which can impact the application's performance. This is a very common problem in microservices architecture as well as mobile clients, where this pattern can be leveraged to reduce the number of calls to backend services. As shown in the following...