Node.js vs .NET APIs 🚀🔥🚀🔥: Exploring the Similarities and Differences

Let us connect:

Support my work:

Hire Me:

WHO AM I:
I'm Mohamad, a Enterprise Architect working in Manchester, UK. I make videos about web, cloud, desktop and mobile development.

GET IN TOUCH:

#dotnet #nodejs #api

[osmantas]

Yesterday I've asked to ardalis compare his fast endpoints with nextjs? Some parts are answered here. Thx

[mirceahanghiuc]

No need for bodyParser if you send the name in query params as you did to the c# app:
var express = require('express');
var app = express();

app.get('/', function(req, res){
res.send('hello ' + req.query.name);
});

app.listen(3000);

[PeterAkaliro]

You don't need body parser to parse json in express. Express comes pre-built with express.json() middleware for parsing JSON.

[fadfooood]

There will be a lot of OOP and Interface gymnastics when the application gets bigger. Node will still be straight forward in my opinion focusing on business and productivity.

[itksports]

How did I not subscribe to your channel

[rokasbarasa]

why not just use :name for the node one? That would be a lot simpler...

[dmsnm]

Not apples to apples comparison considering
In GET, dotnet is sending plain html while node is sending json
In POST, dotnet uses search params while node uses request body for sending data

[mirceahanghiuc]

Node.js and c# classmates, copy homework from me but change a bit to do not be obvious copied. :)

[fernandopoveda]

Var? diference types is low performance.