Skip to content

gRPC vs REST in ASP.NET Core: one catalog served as REST, gRPC, JSON transcoding and gRPC-Web on net10.0 - #2254

Open
vladimir-pecanac-main wants to merge 1 commit into
CodeMazeBlog:mainfrom
vladimir-pecanac-main:seo/125669-grpc-vs-rest-dotnet
Open

vladimir-pecanac-main wants to merge 1 commit into
CodeMazeBlog:mainfrom
vladimir-pecanac-main:seo/125669-grpc-vs-rest-dotnet

Conversation

@vladimir-pecanac-main

Copy link
Copy Markdown
Collaborator

Adds aspnetcore-webapi/GrpcVsRest, a new folder for the new article "gRPC vs REST in ASP.NET Core (with Protobuf vs JSON)".

One ASP.NET Core app on net10.0 serves the same product catalog four ways: a minimal API with System.Text.Json, a gRPC service, the same gRPC service as JSON through gRPC JSON transcoding, and gRPC-Web. One client calls all of them, and BenchmarkDotNet measures message sizes, bytes on the wire and call times.

  • dotnet test runs the two tests (no external services needed).
  • The README lists the commands the article uses (demo, wire, ser, calls).
  • CatalogHost clears the default configuration sources so the benchmark child processes do not bind the app's own ports.

The article is not published yet. This PR stays open until the article goes live.

… and gRPC-Web from one ASP.NET Core app on net10.0)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant