You're reading from Web API Development with ASP.NET Core 8

Product type Book

Published in Apr 2024

Publisher Packt

ISBN-13 9781804610954

Pages 804 pages

Edition 1st Edition

Languages

Concepts

Web Services

Author (1):

Xiaodi Yan

Table of Contents (20) Chapters

Preface

1. Chapter 1: Fundamentals of Web APIs

2. Chapter 2: Getting Started with ASP.NET Core Web APIs

3. Chapter 3: ASP.NET Core Fundamentals (Part 1)

4. Chapter 4: ASP.NET Core Fundamentals (Part 2)

5. Chapter 5: Data Access in ASP.NET Core (Part 1: Entity Framework Core Fundamentals)

6. Chapter 6: Data Access in ASP.NET Core (Part 2 – Entity Relationships)

7. Chapter 7: Data Access in ASP.NET Core (Part 3: Tips)

8. Chapter 8: Security and Identity in ASP.NET Core

9. Chapter 9: Testing in ASP.NET Core (Part 1 – Unit Testing)

10. Chapter 10: Testing in ASP.NET Core (Part 2 – Integration Testing)

11. Chapter 11: Getting Started with gRPC

12. Chapter 12: Getting Started with GraphQL

13. Chapter 13: Getting Started with SignalR

14. Chapter 14: CI/CD for ASP.NET Core Using Azure Pipelines and GitHub Actions

15. Chapter 15: ASP.NET Core Web API Common Practices

16. Chapter 16: Error Handling, Monitoring, and Observability

17. Chapter 17: Cloud-Native Patterns

18. Index

Why subscribe?

19. Other Books You May Enjoy

Updating proto files

gRPC is a contract-first RPC framework. This means that the server and the client communicate with each other using a contract, which is defined in a proto file. Inevitably, the contract will change over time. In this section, we will learn how to update the contract and how to handle the changes in the server and the client.

Once a proto file is used in production, we need to consider backward compatibility when we update the proto file. This is because the existing clients may use the old version of the proto file, which may not be compatible with the new version of the proto file. If the new version of the contract is not backward compatible, the existing clients will break.

The following changes are backward compatible:

Adding new fields to a request message: If the client does not send the new fields, the server can use the default values of the new fields.
Adding new fields to a response message: If the response message contains the new...