I am creating a web api and I am stuck between using asp.net core 2.1 or nodejs' expressjs.

What is your take on this?

take this mind:

this service will also be responsible for processing transactions.

I would take old school language all the way. I’ve used nodejs for front end work only and .net core as my backend, but I’ve never tried backend with nodejs

@devTea they saying a lot of stuff about node's efficiency and it being prone to a lot of errors - It's really confusing but after going through some medium inserts - using a framework that never failed to not disappoint might be a wise choice especially for a large scale application that will have other modules from different infrastructures plugged into it - I think I'll try to encoporate both and see where that will take me - but I'll prioritize (UK English - from RSA btw) using asp.net especially if u dnt have anything negative to say about it - ;D

@SMtengwana my first backend that I focused on is .net too, c# is awesome and the new .net core is amazing as well. Nodejs is probably powerful for some people but it’s rare in my area here

I've built an API with node.js recently. I used Koa as HTTP Server, Joi for input validation, Knex for query building and not to forget JWT. Everything works flawlessly and fast af.

I would recommend against Express.js tho. Check out Koa.js and restify. I went with Koa because its basically express.js on steroids while being less bloated and more asynchronous.

If you go for nodejs look into typescript, it's best of both worlds. It's made by Microsoft and let's you sticly type JavaScript. Most popular NPM modules have support for it and if not then just that part will not have linting if you don't implement it yourself. After using typescript for one of your projects you'll never go back. But if you look for performance nodejs is not that great if not done correctly.

.NET Core. No discussion here.