Learn More
Resend Email
3
rickh
5y

Our lead dev has convinced the board to move the new software suite forward into .Net Core 3. Much of his reasoning is sound, a mainstay of which is the cost and ease of hiring developers to actually make and maintain it.

My own roadmap with the company focuses around one of these products, so I am to become the core developer and maintainer. Given thats the case, given that my primary skill is with Javascript/Node and given that we have deadlines, I am going to make the case today that this product might be better built in Node.

We are going for a microservices architecture. Combined with Typescript for type safety as the code base gets bigger, I am not sure I can think of many real advantages to choosing .NET instead. It will benefit from its async I/O later too, as the plan is to build in API driven dynamic UI down the road.

He is a fierce man, and I am the junior. Wish me luck.

rant

junior

senior

nodejs

braveheart

roadmap

.net core

tech stack
Favorite
Ranter
Comments
  • 2
    5y
    .NET core has async IO since 2.1.

    JS can't do parallel thread, it relies on pending wait on IO completion ports (async IO) to fake multi-threading.
  • 0
    5y
    @nam17887 I hear you, but I might not have been clear enough. There won’t be an actual need for real concurrency, I don’t think. Just many rapid and small transactions; as far as I understand it Node is very good at this for the reasons you mention.
  • 4
    5y
    I have used both .Net Core and Node in production. And if I can choose, I would use Node only for small or very specific projects. For everything that is bigger than a wrapper API (which could be more easily solved with other frameworks) or a bot service I would definitely choose .Net Core (or something else).
    Node is great, but as soon as the project becomes bigger, you start to need more than a few dependencies or it has to scale, it becomes a hell to maintain.
  • 2
    5y
    Would yours be the only Node app in the entire product suite then? If so, that's probably going to be hard to sell.

    Problem is the question you probably have to address is not "Will Node work?" It's "Why won't .NET Core work?" And if Node works, it's very likely that .NET Core will work.
  • 0
    5y
    NET Core will definitely work, but I think it will have a longer development time. By a considerable margin. But yes, it would be the sole Node app if it got approved. This product in particular is more lightweight than the others in terms of demands and functionality.
  • 0
    5y
    @Benedikt very interesting to hear from someone with production experience in both camps. This application is basically a CRUD API that generates financial reports based on quite detailed user input. Quite a few database models etc.
  • 1
    5y
    @platypus lead dev was pretty cool about it, and said some of the thinking was good, apart from the fact that it would make me a single point of failure. I think this may have been what you were alluding to. Anyway, onwards! Time for .NET Core...
Related Rants
devRant © 2021 Hexical Labs LLC
Privacy Policy  |  Terms of Service
Add Comment