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

RPC and GraphQL APIs

While REST-based APIs are widely used in many scenarios today, it is not the only style of web API. For some scenarios, RPC-based APIs or GraphQL APIs may be better suited. It is important to understand the advantages and disadvantages of each style of API so that you can choose the right styles for your scenarios.

What is an RPC-based API?

RPC has existed for many years. It is the earliest, simplest form of web interaction. It is like a local call in some other languages, but it executes over a network. The client is given a list of available methods. Each method takes pre-defined, typed, and ordered parameters, returning a structured response result. So, the client can run on a different machine or in a different process but still work with the server, such as in the same application.

In this way, the client is tightly coupled to the server. If the server changes these methods or any parameters, the client will be affected. Developers must update the...