• 0
    Sounds slow.
  • 1
    @SortOfTested doesn't feel slow to me for 5000 users using my small app.
  • 1
    Nothing personal, it's fine for certain scales and loads, it just won't ever compete with dotnet core on perf for the same workload. Fwiw, I ship a lot of products using node-backed tools, but cut it off at the compiler level.

    Recently had an experience with some shit heels using the same stack. They came off a mobile project that had used it to deliver a phone-gap style app and were super confident.

    They then made a power grab; taking my 180M request/hour, two active node meter sampling services, throwing away my code for political reasons, replacing it with node and then being shocked when it needed 10x the hardware to do the same work. When the shit hit the fan and people weren't getting accurately billed, they insisted there was some magic I wasn't telling them about that would make the fast happen.

    Dutifully spent a week going over their code, cleaned up the slop, corrected their blocking bullshit and sped it up about 3x. Also deleted the unbounded express caching of the reporting dashboard screens which were stored in-memory for every user session with no sticky.

    I was then accused of sabotage when I said they needed more hardware to hit the baseline target. Got into the metrics logs and proved that (shockingly enough) redis and Kafka in the previous system were faster than node writing directly to mongo on every request. Even the process of node reading the final response was 3x slower in dynatrace than the corresponding .Net EDI to poco deserialization.

    Better developers would have made a small difference, but at this point someone brings up any of the node-first stacks, I reach for the garlic and stakes.
  • 2
    @SortOfTested I see exactly what you mean, and I do agree that Node can't really compare with the speed and power of something like .net core. Given the chance I would more than likely take .net any given day. But I have found a particular niche and appeal on Node being that if you are good at it you can definitely bring a lot of satisfaction to customers and development practices because of how free the damned thing is. I am currently evaluating an application using different stacks, Node is one of them and I have enjoyed greatly working with it. Note however that it is not my first time toying with it for a production environment or even using it professionally. I've just always had a sweet spot for Node and subsequently JS, much in the same vein that I've had for C#, which makes the whole thing even harder.
Add Comment