Short answer is yes for most workloads. It's fast, scalable and well supported.
WCF could operate over pipes which was cool for machine local IPC, but beyond that I think gRPC is superior.
But I asked your exact question to the dotnet team and architect David Fowler gave me a decent answer.
> "I don't know that we have a definitive answer as yet and the GRPC experience while great isn't nearly as smooth (as of writing) as the WCF experience. I would say that it's definitely going to be one of the main RPC option of choice going forward but it;s a bit early to say that this is THE blessed new way."
https://github.com/dotnet/core/issues/2278
In .NET Core gRPCdotnet
core
PowerShell2015–2026
dotnet / core
core
.NET news, announcements, release notes, and more!
80Distinct people
86Mentions
0Explicit recommenders
22.1KGitHub stars
What to know before exploring
What it is
.NET news, announcements, release notes, and more!
GitHub
Where it is used
No documented product use was verified in the last source check.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
- dotnet/aspnetcore · linked in 2 of the same discussions
- dotnet/roslyn · linked in 2 of the same discussions
- dotnet/vscode-csharp · linked in 2 of the same discussions
Mentioned in the same Hacker News threads. That is not proof they are substitutes.
This week on Hacker News
Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 12:01:02 AM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year86 dated mentions
Observed mentions: 2015-04-29 21:44:49 UTC to 2026-09-17 14:13:26 UTC.
* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2015 | 2015-01-01 00:00:00 UTC | 2016-01-01 00:00:00 UTC | 3 | 0 | 3 |
| 2016 | 2016-01-01 00:00:00 UTC | 2017-01-01 00:00:00 UTC | 7 | 3 | 4 |
| 2017 | 2017-01-01 00:00:00 UTC | 2018-01-01 00:00:00 UTC | 15 | 3 | 12 |
| 2018 | 2018-01-01 00:00:00 UTC | 2019-01-01 00:00:00 UTC | 6 | 1 | 5 |
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 4 | 0 | 4 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 9 | 1 | 8 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 13 | 1 | 12 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 6 | 4 | 2 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 4 | 1 | 3 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 10 | 4 | 6 |
| 2025 | 2025-01-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 6 | 1 | 5 |
| 2026 (partial) | 2026-01-01 00:00:00 UTC | 2027-01-01 00:00:00 UTC | 3 | 0 | 3 |
From the project README
An excerpt from the repository, fetched Nov 13, 2026.
Read the project’s introduction
.NET Release Notes
Welcome to the home of .NET release notes and news.
Releases
Releases under active support or development:
Version
Release Date
Release type
Support phase
Latest Patch Version
End of Support
.NET 11.0
November 10, 2026
STS
Go-Live
11.0.0-rc.3
November 10, 2026
.NET 10.0
November 11, 2025
LTS
Active
10.0.14
November 14, 2028
.NET 9.0
November 12, 2024
STS
Maintenance
9.0.22
November 10, 2026
.NET 8.0
November 14, 2023
LTS
Maintenance
8.0.33
November 10, 2026
Release notes
Binaries and installers
Installation docs
dotnet-install scripts
Discussions
Follow GitHub Discussions, where you will find the latest news on releases, including PSAs and CVEs.
You can subscribe to discussions with the following RSS feeds:
Category
GitHub Discussions
RSS Feed
All Discussions
🔗
🔗
News
🔗
🔗
General
🔗
🔗
Read the full README on GitHubWhat Hacker News says
4 sourcesThey like to make noise about how crossplatform and opensource .NET Core is, but their debugging infrastructure is actually proprietary. See: https://github.com/dotnet/core/issues/505
In The Evolving Infrastructure of .NET CoreEven when Microsoft does FOSS, they do it in a way that has "proprietary" written all over it. I'm quite excited about writing C# on Linux, but slapping a MIT license on code you release is only half the deal.
Yesterday I decided to write some C# code on Linux. That's easy, I thought: VSCode and .NET Core can both be found in Arch's repos these days. I just have to set an environment variable and edit VSCode's settings to disable telemetry... But alas! It turns out that I need to install Microsoft's proprietary release of Visual Studio Code because the C# debugger is only licensed to work with Visual Studio Code
Here's the Github issue about it, providing a bit of context and a lot of useless discussion: https://github.com/dotnet/core/issues/505
In Microsoft, currently the most valuable company, is having a NadellaissanceAre you allowed to use .NET Core debugging with VSCodium?
https://github.com/dotnet/core/issues/505
In VSCodium – An Open Source Visual Studio Code Without Trackers