---
title: "What replaces WCF in .Net Core?"  
description: "What replaces WCF in .Net Core?"  
author: "Utpal Vishwas"  
published: 2023-07-06  
updated: 2023-07-07  
canonical: https://www.mindstick.com/forum/158987/what-replaces-wcf-in-dot-net-core  
category: ".net core"  
tags: ["asp.net", "asp.net core", ".net core"]  
reading_time: 2 minutes  

---

# What replaces WCF in .Net Core?

What replaces [WCF](https://www.mindstick.com/articles/513/introduction-to-wcf) in .Net Core?

## Replies

### Reply by Aryan Kumar

WCF (Windows Communication Foundation) is a framework for building service-oriented applications. It is a mature framework with a wide range of features, but it is not included in the .NET Core framework.

There are a few different frameworks that can be used to replace WCF in .NET Core. Some of the most popular options include:

- **gRPC:** gRPC is a high-performance, open-source RPC framework that is initially developed by Google. It is based on the HTTP/2 protocol and provides a number of features that make it well-suited for microservices architectures.
- **ASP.NET Core Web API:** ASP.NET Core Web API is a framework for building RESTful APIs. It is a lightweight framework that is easy to use and well-documented.
- **SignalR:** SignalR is a framework for building real-time web applications. It allows you to create applications that can send and receive data in real time, even if the client and server are not on the same machine.

The best framework for you will depend on your specific needs. If you need a high-performance framework with a wide range of features, then gRPC is a good option. If you are looking for a lightweight framework that is easy to use, then ASP.NET Core Web API is a good choice. And if you need to build a real-time web application, then SignalR is a good option.

Here is a table that summarizes the key differences between WCF and the three frameworks mentioned above:

| Feature | WCF | gRPC | ASP.NET Core Web API | SignalR |
| --- | --- | --- | --- | --- |
| Framework type | Full-featured | Microservices | Lightweight | Real-time |
| Supported protocols | HTTP, HTTPS, TCP, UDP | HTTP/2 | HTTP | WebSockets |
| Features | Messaging, security, transactions, routing | Messaging, security, streaming | CRUD operations, routing | Real-time data sharing |
| Complexity | High | Medium | Low | Low |
| Documentation | Extensive | Good | Good | Good |

Ultimately, the best way to choose a framework is to try them out and see which one works best for you. There are a number of tutorials and examples available online that can help you get started.


---

Original Source: https://www.mindstick.com/forum/158987/what-replaces-wcf-in-dot-net-core

Copyright © MindStick Software Pvt. Ltd. This Markdown version is provided for developers, AI systems, and offline reading.