I was reading somewhere (maybe Hackernews itself?) that synchronous programming and/or blocking are actually features and not disadvantages. After working on a huge Node.JS project, I regret taking on anyway (I had to do it for the moolah, aka money). I am now convinced that migrating from Rails to Express (A node.Js framework) was a total mistake. Please note, I do not mean to advertise rails in particular, infact, you can replace rails with anything else thats fits the analogy - perhaps maybe a python framework.
However, this mistake has taught me something(s) very valuable -
1) Don't trade in a tried and tested framework for something like Node.js, that will open up a different level of problems altogether.
2) No matter what language you use, you WILL face issues at scale. Be it Node.js/Scalatra/Rails. You might as well face it with a tried and tested framework.
3) Don't re-write your own framework in something like Go or Haskell or C or C++ or etc. thinking it will be scalable, etc.
You will -
a) Waste massive amounts of time re-inventing the wheel,
b) Open yourself to possibly dangerous security vulnerabilities (Eg: Handling encrypted cookies),
c) Waste your time on things that don't really matter instead of on something that actually matters - The product itself.
4) Anything that you can scale by throwing more money at it is for the win[1]
Why am I talking about scalability, when the discussion is about Async. vs Sync. programming? Because of the reasons many people cite using Node.Js and the like. It's just not worth it. Focus on the product first and the architecture later. This comes from someone who wasted a year of his life doing everything above.
Sorry you had a bad experience, bud. I am on a team of six, all pretty experienced with Node, and we don't have those issues. We've been going production on it for about a year and a half now. People cried a little in the beginning because it was different but now that we have embraced (and love) callbacks, we rip through development pretty quick. Things aren't always done for you but it's getting pretty rare at this point.
Comments
I was reading somewhere (maybe Hackernews itself?) that synchronous programming and/or blocking are actually features and not disadvantages. After working on a huge Node.JS project, I regret taking on anyway (I had to do it for the moolah, aka money). I am now convinced that migrating from Rails to Express (A node.Js framework) was a total mistake. Please note, I do not mean to advertise rails in particular, infact, you can replace rails with anything else thats fits the analogy - perhaps maybe a python framework.
However, this mistake has taught me something(s) very valuable -
1) Don't trade in a tried and tested framework for something like Node.js, that will open up a different level of problems altogether.
2) No matter what language you use, you WILL face issues at scale. Be it Node.js/Scalatra/Rails. You might as well face it with a tried and tested framework.
3) Don't re-write your own framework in something like Go or Haskell or C or C++ or etc. thinking it will be scalable, etc.
You will -
a) Waste massive amounts of time re-inventing the wheel,
b) Open yourself to possibly dangerous security vulnerabilities (Eg: Handling encrypted cookies),
c) Waste your time on things that don't really matter instead of on something that actually matters - The product itself.
4) Anything that you can scale by throwing more money at it is for the win[1]
Why am I talking about scalability, when the discussion is about Async. vs Sync. programming? Because of the reasons many people cite using Node.Js and the like. It's just not worth it. Focus on the product first and the architecture later. This comes from someone who wasted a year of his life doing everything above.
[1]http://highscalability.com/blog/2013/4/15/scaling-pinterest-...
Sorry you had a bad experience, bud. I am on a team of six, all pretty experienced with Node, and we don't have those issues. We've been going production on it for about a year and a half now. People cried a little in the beginning because it was different but now that we have embraced (and love) callbacks, we rip through development pretty quick. Things aren't always done for you but it's getting pretty rare at this point.