Why we moved from NodeJS to Ruby on Rails

#1

Post by heroic » Mon, May 14, 2012, 4:52 PM UTC

Why we moved from NodeJS to Ruby on Rails
blog.targeterapp.com

Re: Why we moved from NodeJS to Ruby on Rails

#2

Post by mcantelon » Mon, May 14, 2012, 5:00 PM UTC

I wonder what testing functionality, specifically, they see missing in the Node ecosystem...

Re: Why we moved from NodeJS to Ruby on Rails

#3

Post by semarjt » Mon, May 14, 2012, 5:03 PM UTC

>I am huge fan of NodeJs and I believe it’s a very technology and we will see it getting

I think you accidentally word.

Re: Why we moved from NodeJS to Ruby on Rails

#4

Post by heroic » Mon, May 14, 2012, 5:04 PM UTC

mcantelon wrote: post #2

I wonder what testing functionality, specifically, they see missing in the Node ecosystem...

I presume it would be something related to capybara, rspec and factory girl.

Re: Why we moved from NodeJS to Ruby on Rails

#5

Post by FooBarWidget » Mon, May 14, 2012, 5:06 PM UTC

mcantelon wrote: post #2

I wonder what testing functionality, specifically, they see missing in the Node ecosystem...

I'm writing a server in Node and to date I'm still trying to figure out how to control the main loop from Node. I want to write tests like this:

    1. register some timers and create some sockets
    2. send some stuff over the sockets
    3. wait until the socket handlers received some data which cause the handlers to unregister the sockets and timers
    4. at this point, the main event loop has ended. go to next test and setup a new event loop

How do you do (3) and (4) in Node? I have no idea, and I couldn't find any clear answers on the Internet. I ended up writing my tests in RSpec which launch Node processes, and I just check whether the stuff printed to stdout matches what I expect. RSpec also happens to have a much much nicer syntax than any Javascript testing framework I've encountered.

Re: Why we moved from NodeJS to Ruby on Rails

#6

Post by sushi » Mon, May 14, 2012, 5:06 PM UTC

semarjt wrote: post #3

>I am huge fan of NodeJs and I believe it’s a very technology and we will see it getting I think you accidentally word.

Thanks. Fixed now.

Re: Why we moved from NodeJS to Ruby on Rails

#7

Post by jarin » Mon, May 14, 2012, 5:07 PM UTC

This is why it's good to have a lot of tools in your toolbox. Everything has its strengths and weaknesses.

Re: Why we moved from NodeJS to Ruby on Rails

#8

Post by bergie » Mon, May 14, 2012, 5:09 PM UTC

FooBarWidget wrote: post #5

mcantelon wrote: post #2

I wonder what testing functionality, specifically, they see missing in the Node ecosystem...

I'm writing a server in Node and to date I'm still trying to figure out how to control the main loop from Node. I want to write tests like this: 1. register some timers and create some sockets 2. send some stuff over the sockets 3. wait until the socket handlers received some data which cause the handlers to unregister the sockets and timers 4. at this point, the main event loop has ended. go to next test and setup a…

That sounds like a complicated approach at it. Here's an example of some NodeUnit tests that involve communications with a Redis-based message queue:

https://github.com/bergie/noflo/blob/master/test/MQ_SendMess...

More BDD-ish version of something similar:

https://github.com/nemein/kckupmq/blob/master/test/001_kckup...

Re: Why we moved from NodeJS to Ruby on Rails

#9

Post by Timmy_C » Mon, May 14, 2012, 5:12 PM UTC

The argument he makes is that it boils down to maturity. One framework is still evolving and the other is more mature.

Re: Why we moved from NodeJS to Ruby on Rails

#10

Post by EternalFury » Mon, May 14, 2012, 5:16 PM UTC

Does anyone know 1 major consumer-facing site that was able to scale with Rails?

I know Twitter kind of had to move away from Rails due to scalability issues.

GameBattles.com also had to back away from Rails after their uptime dropped to 80%.

I am not trying to tarnish Rails, I am just curious to learn about some success stories involving Rails at very large scale.