3 ms·

We are in the process of switching a project from Torquebox to Passenger. We spent a lot of time having to fix issues here and there, tweak our chef recipes, a

by dylanz 14y ago

We are in the process of switching a project from Torquebox to Passenger. We spent a lot of time having to fix issues here and there, tweak our chef recipes, and, on top of it, the startup time of JRuby was painful. I'm a huge fan of JRuby and Torquebox, and I hope they do really well. We're a startup, so we need the devops effort to be minimal and the development time to be extremely speedy. I hope we're able to migrate over to JRuby one day in the future after we release.

gnufied 14y ago
Interesting, so you are not only switching to Passenger but switching to MRI as well? I think it might be worth dropping an Email to JRuby mailing list (https://github.com/jruby/jruby/wiki/MailingLists https://github.com/jruby/jruby/wiki/MailingLists), if you haven't already about what troubles you faced and why you are switching.
sandGorgon 14y ago
really am curious on why you are doing that. Am going to be beginning a new project on jruby.
dylanz 14y ago
There are a few reasons we're making the switch, and I'll try and jot down a bunch of them here. I'll also duplicate this information and let the JRuby guys know as well. A little background, I've used JRuby on a few projects, have contributed to the project, some gems, have attended some JRuby conferences, etc. I'm a huge fan of JRuby and its community. That said, here are some reasons we're making the switch: - Start up time. It starts to sting after a while when frequently firing up console and compiling assets. - Gems compatibility. For the most part, this is a non-issue, but we had to do some JRuby related patches to some gems (hstore support for postgres, and some others that I can't think of off the top of my head). - Torquebox. It's a solid project, but we had a bunch of small issues that we can into that made it a bit painful. Weird terminal buffering on console (same thing for ruby-debug), requests dropping on restarts, and some other issues. The baked in backgrounding and the stomplet support is really nice, but we decided to sacrifice these things for something that we understand a lot better (we have a lot more experience with the ruby servers than the JBoss and other java application servers). A lot of it boils down to us not having the time to learn and fix the issues we were running into w/ the JRuby deployment. We need to focus on building our application, so we don't have the luxury of learning a new deployment ecosystem. That said, we are using AngularJS, so there is "one" thing new that we're all learning.

by dylanz 14y ago

gnufied 14y ago

Interesting, so you are not only switching to Passenger but switching to MRI as well? I think it might be worth dropping an Email to JRuby mailing list (https://github.com/jruby/jruby/wiki/MailingLists https://github.com/jruby/jruby/wiki/MailingLists), if you haven't already about what troubles you faced and why you are switching.

sandGorgon 14y ago

really am curious on why you are doing that. Am going to be beginning a new project on jruby.

dylanz 14y ago

There are a few reasons we're making the switch, and I'll try and jot down a bunch of them here. I'll also duplicate this information and let the JRuby guys know as well. A little background, I've used JRuby on a few projects, have contributed to the project, some gems, have attended some JRuby conferences, etc. I'm a huge fan of JRuby and its community. That said, here are some reasons we're making the switch: - Start up time. It starts to sting after a while when frequently firing up console and compiling assets. - Gems compatibility. For the most part, this is a non-issue, but we had to do some JRuby related patches to some gems (hstore support for postgres, and some others that I can't think of off the top of my head). - Torquebox. It's a solid project, but we had a bunch of small issues that we can into that made it a bit painful. Weird terminal buffering on console (same thing for ruby-debug), requests dropping on restarts, and some other issues. The baked in backgrounding and the stomplet support is really nice, but we decided to sacrifice these things for something that we understand a lot better (we have a lot more experience with the ruby servers than the JBoss and other java application servers). A lot of it boils down to us not having the time to learn and fix the issues we were running into w/ the JRuby deployment. We need to focus on building our application, so we don't have the luxury of learning a new deployment ecosystem. That said, we are using AngularJS, so there is "one" thing new that we're all learning.