Skip to content

I want to create a highly performant API - can anyone from recommend C# learning tips or resources?

github logo ใƒป1 min read  

If you wanted to make a highly performant API that writes and reads a lot of data, what language would you choose? C# seems to be the common answer I'm getting.

Has anyone from learned C# from a JS background, and if so, do you have any learning tips or resources? I have about $500 learning budget.

twitter logo DISCUSS (5)
markdown guide

I'm assuming everyone saying C# is referring to ASP.NET Core, which is a very fast web framework.

Free: Microsoft Virtual Academy

My personal paid recommendation: Plurlarsight

Jeff Fritz's livestream is also a great resource for learning ASP.NET Core:
Youtube VoDs
Twitch Channel


Apologies for my late reply Sam. Thanks a lot!


If you wanted to make a highly performant API that writes and reads a lot of data, what language would you choose?

The language you like most and are best at, provided it's reasonably popular, probably has ways of meeting your performance needs.

So, for me, I'd go with Python unless I wanted to learn something else or had external reasons for using something else. Rust is popular and growing right now, has some interesting features I'm curious about, and is rumored to have a great community, so I might choose it for an excuse to learn about that. If I wanted it to be mainly used or appreciated by Java developers, I'd choose Java, or at least a JVM language.

How much data is "a lot" and what kind of API? Do you want it to be a REST interface for client programs to call remotely, or do you want it to be a library for reading/writing locally to files, a database, or a device?

C# seems to be the common answer I'm getting.

Did they give their reasoning? It's probably a great choice if you're going to be talking to Microsoft-based services, applications, or people.

I've used C# a bit, but I mainly winged it due to its similarity to Java (in some ways it improved on Java, though Java may have caught up by now), so I don't have any good resources to suggest.


Apologies for my late reply too, Dustin. In my case, that's JS - and I did end up using Node.js for a large part of the current internal API. Still, using TypeScript where possible and commenting well from the start should keep it future-proof to change to something like C# in the future from someone more experienced.

Or not at all! Haha


Of course, I'd prefer free resources to paid - I'm just willing to invest more than effort in this.

Classic DEV Post from May 8 '19

Resolving tricky situations with git reset and rebase ๐Ÿงถ

You should care about how clean your Git history is. It provides a way to communicate changes to a codebase with other developers who you are working with, but doing so requires some thought and intention. Ever seen one as clean as this?

James Scaur profile image
I build customer support tools for cryptocurrency exchanges. Check out and

The only way to keep up with JavaScript trends is with the help of community.

Join โค๏ธ