I had the same question and ended up with Node, just because there are a lot of resources and a big community to help. Also, I can't share code between server and app, so I can't save code by using Dart on the server. But in the end both can be used and is your choice, none is better. If you go with Dart, I recommend you to check out https://aqueduct.io/

There is also Angel: https://angel-dart.github.io

People tend to ignore it in these conversations (which frankly, is often disheartening), but it’s been used in production, and is nearly done with a large upgrade.

(disclaimer: I am the creator)

Thanks for sharing and great job btw! I will give it a try soon.

Not sure why you say you can't share code between server and app: if the code is in a common library that both import, it can be shared.

I mean, in my case i can share some utilities, but most of the code is just too specific to client/server.

Thank you for your comment. I tried aqueduct, but at the end, I felt node is the right choice (for now).

Hey LawZ, thanks for sharing your resolve. Perhaps you could shed a bit more light on your decision.

Also, would it not be better to save yourself the context-switching between ecosystems and sticking with Dart?

I made a YouTube video series on Aqueduct and would love to gather your thoughts: https://youtu.be/vvDomA-ru3E

Depends on what you want to do on the server side. For many, it is enough to have a Postgresql database backend, and a very limited amount of other services needed, in such cases Dart is great for server side.

If you rely on many third-party services, chances are that the client API coverage is not that great, and you are better off with node at this point.