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

Co-hosting silos with ASP.NET core

Typically, an Orleans application is intended to run the core business functionality. Handling cross-cutting concerns, authentication, authorization, request throttling, and so on is not the primary responsibility of Orleans. So, it is recommended not to have direct interactions between external clients and Orleans silos. There should be a gateway before the Orleans application that routes the user requests. The Orleans application should not directly take the user requests.

Figure 4.11 – Orleans N-tier application

Consider a traditional N-tier architecture as shown in the preceding figure. Each tier is physically separated and will mostly be running on different machines. Here, the service tier will be the interfacing layer to the business layer built in Orleans. The service layer takes the user requests coming from the presentation tier and processes them by interacting with the business tier built in Orleans. The...