Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. General Programming
  3. Design and Architecture
  4. Node.js : Non-blocking thing

Node.js : Non-blocking thing

Scheduled Pinned Locked Moved Design and Architecture
javascriptsysadminapachewindows-adminperformance
43 Posts 6 Posters 44 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • J jschell

    Eytukan wrote:

    Micro-services, mainly after Node took over, YES, it's changing the landscape of a Web-server "module" & distributed computing.

    Where "it" is what exactly? Micro-services? Micro-services are a really, really good way to end up in a world of hurt down the road. Not sure if most developers realize that but I have seen bad implementations of that and I am hopeful that others recognize that the required architecture (not technology) required to get it right slow them down or stop them before they attempt it.

    E Offline
    E Offline
    Eytukan
    wrote on last edited by
    #41

    I was actually adding this point in my previous reply. But I felt, I shouldnt speak more about a tech that I haven't worked on in detail. I'm just starting to use Node/Microservices. But there's precisely the problems popping up, making us think about how we need to share data across instances, how to sync them in real time & all that. I also do see, for every problem, there's a way and teams are getting to go past it. Micro-services , for sure is over-marketed. But it definitely has a considerable goodness too.

    Full Reset

    J 1 Reply Last reply
    0
    • E Eytukan

      I was actually adding this point in my previous reply. But I felt, I shouldnt speak more about a tech that I haven't worked on in detail. I'm just starting to use Node/Microservices. But there's precisely the problems popping up, making us think about how we need to share data across instances, how to sync them in real time & all that. I also do see, for every problem, there's a way and teams are getting to go past it. Micro-services , for sure is over-marketed. But it definitely has a considerable goodness too.

      Full Reset

      J Offline
      J Offline
      jschell
      wrote on last edited by
      #42

      Just noting that I didn't see anything in your response about how the architecture is being handled. If a company does in fact have sufficient traffic or at least a reasonable (actual) expectation that they will have it in the future then if they fail at the architecture for the microservices then they will end up with serious problems. The architecture must start with a very solid and detailed understanding of what the actual (not hypothetical) load of the business will be with real (again not hypothetical) load dynamics will be. If that doesn't happen then 5 years down the road what the company ends up with is what started as an amusement for the developers (no business value) and now a maintenance problem on top of all the other maintenance problems that usually accumulate with legacy code.

      1 Reply Last reply
      0
      • L Lost User

        This might be news, but CodeProject has more .NET related articles :)

        Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^] "If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.

        L Offline
        L Offline
        Lutoslaw
        wrote on last edited by
        #43

        Eddy Vluggen wrote:

        This might be news, but CodeProject has more .NET related articles

        Well now it's Code Project: For those who code. But when I joined the community back in 2005 it was Code Project: Your Visual Studio and .NET home page. So yeah maybe it roars like a lion now, but nonetheless still a kitty inside.

        1 Reply Last reply
        0
        Reply
        • Reply as topic
        Log in to reply
        • Oldest to Newest
        • Newest to Oldest
        • Most Votes


        • Login

        • Don't have an account? Register

        • Login or register to search.
        • First post
          Last post
        0
        • Categories
        • Recent
        • Tags
        • Popular
        • World
        • Users
        • Groups