product. Best use-case is quite limited: heavy on I/O, APIs, streaming data. Requires signiﬁcant conﬁguration time to get running on a server. Not ready “out of the box.” Testing frameworks are not robust. NODE.JS The Cons (http://blog.targeterapp.com/post/22984987832/ why-we-moved-from-nodejs-to-ror) Serene Careaga @grrlcoder
object-oriented language. An active community that oﬀers a lot of support, documentation and tools. (See: Railscast, Ruby Toolbox, etc.) Full ecosystem that allows for seamless vertical integration. Rapid deployment. So. Many. Freaking. Gems. Serene Careaga @grrlcoder
be diﬃcult to maintain. Scalability concerns (note: ORM/query problems often the cause). Rails is always evolving. This can be diﬃcult for app maintenance and taxing on developers. High learning curve: must learn Ruby, Rspec (or prefered TDD), SASS, Coﬀee Script to get your app functional.
array of web products: membership-based sites, CMSs, complex interactive sites. You have an urge to test, frequently. MVC design logic and database usage are critical to application functionality. All the things! (Joking.) Serene Careaga @grrlcoder
can conﬁgure Rails to run as a single-process, event-driven architecture with EventMachine. http://rubyeventmachine.com/ You can also conﬁgure Node.js to run Ruby. (Plus, don’t forget Express.js for framework functionality!) https://devcenter.heroku.com/articles/realtime-polyglot-app-nod e-ruby-mongodb-socketio