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[
^]