Hey I'm struggling with this same decision, and the path is somewhat time consuming-- the hurdles don't at all seem up-front :-( Solo developer here, so my decision making criteria: enjoying spending time getting a solid understanding of the situation before starting, but must be able to make rapid/agile changes quickly in the future.
As it stands, these appear to be my main choices: 1: go with heroku! good: - easy, familiar, reliable, maintenance-free hosting - a slew of tools and addons readily available - easy expansion and good support - familiar ruby, not jruby - separation of data layer may be kind of nice - chance to contribute to something new & open source - perhaps a more agnostic solution, allowing polyglot persistence smoothly bad: - no rails integration has been put together yet, work for integrating models would be required (validation, etc) - some unknown additional overhead & maintenance in designing internal REST API - some unknown slowness may be invoked over http - some unknown memory overheads with plugins may be invoked - some unknown tools may or may not exist - some unknown issues in moving to own database server in the (probably quite distant) future 2: jruby/embedded database good: - model integration already exists - faster to some unknown degree bad: - must find new webhost, try for one that's not a time or money drain If there are good hastle-free jruby hosting services with a free plan, the choice would be self-evident. Do you have favorites? Unless there are other things I'm missing. Thoughts? Thanks, --Peter PS: I'm quite excited to try neo4j out! -- View this message in context: http://neo4j-community-discussions.438527.n3.nabble.com/Re-Neo4j-Heroku-Beta-Neo4j-A-Rails-Example-tp3250334p3271828.html Sent from the Neo4j Community Discussions mailing list archive at Nabble.com. _______________________________________________ Neo4j mailing list [email protected] https://lists.neo4j.org/mailman/listinfo/user
