.net core REST API vs WCF which one is faster?

Question

0.00/5 (No votes)

See more:

Hi All,

I am new to .NET Core. I am working on a new project where we will have REST APIs that should be used by thousands of users at the same time. The REST APIs will use Entity Framework to update and return data from a SQL server database. We use Unit tests and logging(log4net) extensively.

from my research online I found that dot net core does not have all the dot net framework APIs.

I have a few concerns

1- Will a dot net core REST API be faster than WCF REST API?
2- Does dot net core support unit testing and logging?
3- what are the main features that are missing in dot net core?

What I have tried:

I have searched online for answers to the above questions but I did not find a definitive answer

Posted 6-Sep-18 4:54am

Member 13975267

Updated 20-Sep-19 15:50pm

Add a Solution

2 solutions

Solution 1

1. Impossible to guess as it depends on so many variables.
2. dot net core support unit testing and logging - Google Search[^].
3. You need to be more specific.

Posted 6-Sep-18 5:23am

Richard MacCutchan

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Vincent Maverick Durano · Accepted Answer · 2018-09-06T08:03:00

Quote:
I found that dot net core does not have all the dot net framework APIs.

True but the latest version of .NET Core should include the core features and APIs you need to get you started and build the app. Keep in mind that the .NET Core framework is designed to be cross-platform, so you don't expect windows-specific APIs will be available. Also, you have to consider and analyze why you need to use .NET Core over the full .NET framework. If you are aiming for cross-platform, microservices arch approach along with Containers, then .NET Core should fit perfectly for that.

Quote:
1- Will a dot net core REST API be faster than WCF REST API?

There is no definitive answer to your question, it all depends on what kind of traffic are you expecting (or wanting to serve), what kind of functionality would your REST API have (which also impacts performance), how you built it (code standards and best practices) and lots more.

Here's a good article that you might want to read: ASP.NET Frameworks and Raw Throughput Performance - Rick Strahl's Web Log[^]

In the recent version of .NET Core, there are lots of performance optimization and enhancements made to the framework. It also implements .Net Standard that makes it easy to share the codes with other versions of .Net Core. If I were to choose, I would definitely go with ASP.NET Core Web API (REST) since you are aiming to use .NET Core.

Quote:
2- Does dot net core support unit testing and logging?

As already mentioned in the other solution, .NET Core does support both unit testing and logging. ASP.NET Core is all about middlewares, so you can use and inject a Unit test and Logging framework that you prefer to your app.

Quote:
3- what are the main features that are missing in dot net core?

Start looking at the new features added to the new version here: What's new in .NET Core 2.1 | Microsoft Docs[^]

and then look at the road-map for the missing piece you're after here:

(a) core/roadmap.md at master · dotnet/core · GitHub[^]
(b) Roadmap · aspnet/Home Wiki · GitHub[^]