On 23/01/2012, at 4:27 PM, Xavier Shay wrote: > Sorry this thread is kind of old but I wanted to weigh in, hope it's not too > late to be relevant.
It's awesome to see your reply here. I wish you'd pop up earlier as it looks like I went through similar pain points :) > We started embedding neo4j inside JRuby but quickly switched to the > stand-a-lone server. Massive stability and corruption issues with the > embedded one the moment we sent even a trifling production load at it. This > was on 1.4 and 1.5rc1, so perhaps things are a little better now. There are still weird issues sometimes popping up. > Embedded is useful for once off batch loads to get you started though. Protip > for this: use the java classes directly, don't try to use the neo4j ruby gem > abstraction (use it to give you access to the java classes though: require > it, just don't use any of its ruby classes.) This way you can copy all the > examples from the manual and not have to worry about Weird Stuff. Ohh, man. I spent a LOT of time submitting PRs to neo4j.rb, got commit access to the repo an publishing the gem. But last Friday just gave up on the whole neo4j+JRuby idea. Great in theory, too much pain in practice. And I didn't even get to production. > Neology works fine for us even though it's a little cruft. It's a trivial > wrapper on top of HTTP so not much to go wrong. I wonder how do you wrap the models/services/logic with it. It's a bit infortunate to lose all the goodness of Rails with ActiveRecord/DataMapper. Neo4j.rb does the job there. I asked about it it http://stackoverflow.com/questions/8335136/which-ruby-rest-api-client-for-neo4j Then I started my own wrapper (https://github.com/dnagir/morpheus) but then drifted to much from what I thought to do and gave it up. (Then also gave on on CanCan with embedded neo4j.rb in favour of my own https://github.com/dnagir/allowy). > In general, develop on MRI, deploy to JRuby, run CI over both and you won't > go too far wrong after some initial teething problems. I gave a talk at the > JRuby meetup here last week, it was recorded so hopefully will be published > soon. I feel like I'd rather deploy on MRI too. Don't have huge traffic and stuff, so "enterprise grade" server isn't a requirement. I have been waiting for the recording since EngineYard first announce it :) So hope it will be published indeed. -- You received this message because you are subscribed to the Google Groups "Ruby or Rails Oceania" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rails-oceania?hl=en.
