Unicorn has a number of failsafes built in, but if your server is slow you can start getting problems as a result.
Reverse-proxying can help, but a limited amount.
Neo4J looks neat, but it's High-Availability stuff looks dubious, so we didn't wind up using it at work -- we're using raw Cassandra, mostly, and we looked at Titan, a Cassandra-backed graph DB.
Mongrel2 is really cool, and a ZeroMQ-backed web server is a really good idea. There are a number of practical problems with some of Mongrel2's specific implementation, though. It looks like a great idea that could be amazing with more polish, but the polish isn't there yet.
From: Adrien <[address removed]>
To: [address removed]
Sent: Friday, November 9,[masked]:30 AM
Subject: Re: [ruby-81] stack: Passenger vs Unicorn
>>Yeah I was just confused since he wrote jRuby - guess it was a typo
>>Yup, stoked about deploying Torquebox as you saw from my email haha. Can finally leverage all my java friends for help :)
Using JRuby will also allow you to use Neo4J (graphing database/NoSQL that runs on JVM.)
Jose Valim is developing a new webserver as part of his Elixir project (enhanced Erlang) that will be worth looking into. And Zed Shaw is working on Mongrel2. But both of those are down the road a bit.
I'm hoping reverse proxying will take care of slower client connections, my public facing Rails apps aren't doing any file uploading. I thought Unicorn had a good amount of fail safes built in, will have to revisit the docs.
Please Note: If you hit "REPLY", your message will be sent to everyone on this mailing list ([address removed])
This message was sent by Adrien ([address removed]) from The East Bay Ruby Meetup Group.
To learn more about Adrien, visit his/her member profile
Set my mailing list to email me As they are sent | In one daily email | Don't send me mailing list messages
Meetup, PO Box 4668 #37895 New York, New York[masked] | [address removed]