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

Questions

  1. What is the Liskov substitution principle?

A. Base class instances should be replaceable with instances of their derived type.

B. Derived class instances should be replaceable with instances of their base type.

C. Designing for generics that can work with any data type.

Answer – A

  1. What is the single responsibility principle?

A. Instead of one common large interface, plan for multiple scenario-specific interfaces for better decoupling and change management.

B. You should avoid taking a direct dependency on a concrete implementation; instead, you should depend on abstractions as much as possible.

C. An entity should only have a single responsibility. You should avoid giving one entity multiple responsibilities.

D. Entities should be designed in such a way that they should be open for extension but closed for modification.

Answer – C

  1. What is the open closed principle?

A. Open to modification, but closed...