You're reading from Microservices Communication in .NET Using gRPC A practical guide for .NET developers to build efficient communication mechanism for distributed apps

Product type Paperback

Published in Feb 2022

Publisher Packt

ISBN-13 9781803236438

Length 486 pages

Edition 1st Edition

Languages

Tools

.NET

Concepts

Microservices

Author (1):

Fiodar Sazanavets

Preface

1. Section 1: Basics of gRPC on .NET

2. Chapter 1: Creating a Basic gRPC Application on ASP.NET Core FREE CHAPTER

3. Chapter 2: When gRPC Is the Best Tool and When It Isn't

4. Chapter 3: Protobuf – the Communication Protocol of gRPC

5. Section 2: Best Practices of Using gRPC

6. Chapter 4: Performance Best Practices for Using gRPC on .NET

7. Chapter 5: Applying Versioning to the gRPC API

8. Chapter 6: Scaling a gRPC Application

9. Section 3: In-Depth Look at gRPC on .NET

10. Chapter 7: Using Different Call Types Supported by gRPC

11. Chapter 8: Using Well-Known Types to Make Protobuf More Handy

12. Chapter 9: Securing gRPC Endpoints in Your ASP.NET Core Application with SSL/TLS

13. Chapter 10: Applying Authentication and Authorization to gRPC Endpoints

14. Chapter 11: Using Logging, Metrics, and Debugging in gRPC on .NET

15. Assessments

16. Other Books You May Enjoy

Questions

Why would you need load balancing?
1. To improve the application performance
2. To split queries into smaller sub-queries
3. To split a large number of requests between multiple instances of the application
4. To protect your server-side components from hacking
How is client-side load balancing done?
1. By sending requests to a server endpoint, which then redirects the call
2. By getting the server hostname resolved into a list of IP addresses
3. By getting the list of individual endpoint addresses and calling them directly
4. By trying to call all addresses specified in the local DNS configuration
Which one of these is a valid type of load balancing?
1. Connecting to endpoints in a round-robin fashion
2. Connecting to the first available endpoint
3. Connecting to endpoints at random
4. All of the above
How does a proxy load balancer work?
1. The client connects to the proxy endpoint and the proxy redirects it to individual application instances.
2. The client requests the full list of addresses from the proxy...

The rest of the chapter is locked