We are working in python and our webapp is almost beta launch ready.
We were planning on using neo4j before starting but due to some problems we had to move away from it.
Now situation is such that we can use neo4j again and the debate is python REST or Scala with embedded.
I am in favour that python REST is slow but not that slow that we need to port to entirely different language just for the sake of embedded and I also read when neo4j needs to be moved standalone on a separate server REST will come into play again.
REST is usually fast enough, esp for a Web app's access patterns.
Use Gremlin for server-side scripting to combine multiple HTTP requests into one transactional request -- Bulbs/Python ( https://github.com/espeed/bulbs) was designed for this purpose and is very Gremlin-centric.
Bulbs was built with Flask in mind because Flask isn't tied to an ORM, but it's generic and works with any Python Web framework.
The Bulbs 0.3 docs are coming soon. Look at Ligthbulb ( https://github.com/espeed/lightbulb) for more examples -- it will be used in the upcoming docs as an example app.
On Thursday, March 15, 2012 1:10:31 PM UTC-6, Manav Goel wrote:
> We are working in python and our webapp is almost beta launch ready.
> We were planning on using neo4j before starting but due to some > problems we had to move away from it.
> Now situation is such that we can use neo4j again and the debate is > python REST or Scala with embedded.
> I am in favour that python REST is slow but not that slow that we need > to port to entirely different language just for the sake of embedded > and I also read when neo4j needs to be moved standalone on a separate > server REST will come into play again.
If you decide for REST, you can also use neo4restclient, it provides a low level library and it's designed to be as similar as possible to the official python-embeded driver, thus, trying to have the same API. It supports extensions like Cypher or Gremlin, indexes with complex lookups using composition of Lucene fulltext queries, and transactions wrapped through the batch REST operation.
On Thu, Mar 15, 2012 at 15:38, James Thornton <james.thorn...@gmail.com> wrote:
> REST is usually fast enough, esp for a Web app's access patterns.
> Use Gremlin for server-side scripting to combine multiple HTTP requests > into one transactional request -- Bulbs/Python > (https://github.com/espeed/bulbs) was designed for this purpose and is very > Gremlin-centric.
> Bulbs was built with Flask in mind because Flask isn't tied to an ORM, but > it's generic and works with any Python Web framework.
> The Bulbs 0.3 docs are coming soon. Look at Ligthbulb > (https://github.com/espeed/lightbulb) for more examples -- it will be used > in the upcoming docs as an example app.
> - James
> On Thursday, March 15, 2012 1:10:31 PM UTC-6, Manav Goel wrote:
>> We are working in python and our webapp is almost beta launch ready.
>> We were planning on using neo4j before starting but due to some >> problems we had to move away from it.
>> Now situation is such that we can use neo4j again and the debate is >> python REST or Scala with embedded.
>> I am in favour that python REST is slow but not that slow that we need >> to port to entirely different language just for the sake of embedded >> and I also read when neo4j needs to be moved standalone on a separate >> server REST will come into play again.
> If you decide for REST, you can also use neo4restclient, it provides a > low level library and it's designed to be as similar as possible to the > official python-embeded driver, thus, trying to have the same API. It > supports extensions like Cypher or Gremlin, indexes with complex > lookups using composition of Lucene fulltext queries, and > transactions wrapped through the batch REST operation.
> On Thu, Mar 15, 2012 at 15:38, James Thornton <james.thorn...@gmail.com> > wrote:
> > REST is usually fast enough, esp for a Web app's access patterns.
> > Use Gremlin for server-side scripting to combine multiple HTTP requests > > into one transactional request -- Bulbs/Python > > (https://github.com/espeed/bulbs) was designed for this purpose and is > very > > Gremlin-centric.
> > Bulbs was built with Flask in mind because Flask isn't tied to an ORM, > but > > it's generic and works with any Python Web framework.
> > The Bulbs 0.3 docs are coming soon. Look at Ligthbulb > > (https://github.com/espeed/lightbulb) for more examples -- it will be > used > > in the upcoming docs as an example app.
> > - James
> > On Thursday, March 15, 2012 1:10:31 PM UTC-6, Manav Goel wrote:
> >> We are working in python and our webapp is almost beta launch ready.
> >> We were planning on using neo4j before starting but due to some > >> problems we had to move away from it.
> >> Now situation is such that we can use neo4j again and the debate is > >> python REST or Scala with embedded.
> >> I am in favour that python REST is slow but not that slow that we need > >> to port to entirely different language just for the sake of embedded > >> and I also read when neo4j needs to be moved standalone on a separate > >> server REST will come into play again.
> On Thu, Mar 15, 2012 at 10:51 PM, Javier de la Rosa <ver...@gmail.com > <mailto:ver...@gmail.com>> wrote:
> If you decide for REST, you can also use neo4restclient, it provides a > low level library and it's designed to be as similar as possible > to the > official python-embeded driver, thus, trying to have the same API. It > supports extensions like Cypher or Gremlin, indexes with complex > lookups using composition of Lucene fulltext queries, and > transactions wrapped through the batch REST operation.
> On Thu, Mar 15, 2012 at 15:38, James Thornton > <james.thorn...@gmail.com <mailto:james.thorn...@gmail.com>> wrote:
> > REST is usually fast enough, esp for a Web app's access patterns.
> > Use Gremlin for server-side scripting to combine multiple HTTP > requests > > into one transactional request -- Bulbs/Python > > (https://github.com/espeed/bulbs) was designed for this purpose > and is very > > Gremlin-centric.
> > Bulbs was built with Flask in mind because Flask isn't tied to > an ORM, but > > it's generic and works with any Python Web framework.
> > The Bulbs 0.3 docs are coming soon. Look at Ligthbulb > > (https://github.com/espeed/lightbulb) for more examples -- it > will be used > > in the upcoming docs as an example app.
> > - James
> > On Thursday, March 15, 2012 1:10:31 PM UTC-6, Manav Goel wrote:
> >> We are working in python and our webapp is almost beta launch > ready.
> >> We were planning on using neo4j before starting but due to some > >> problems we had to move away from it.
> >> Now situation is such that we can use neo4j again and the debate is > >> python REST or Scala with embedded.
> >> I am in favour that python REST is slow but not that slow that > we need > >> to port to entirely different language just for the sake of > embedded > >> and I also read when neo4j needs to be moved standalone on a > separate > >> server REST will come into play again.
No - neo4j-scala is a client lib for Scala that supports embedded Neo4j DBs and via java-rest-binding a REST based server access. So these suggestions are valid if you go for Scala...
> On Thu, Mar 15, 2012 at 10:51 PM, Javier de la Rosa <ver...@gmail.com>wrote:
>> If you decide for REST, you can also use neo4restclient, it provides a >> low level library and it's designed to be as similar as possible to the >> official python-embeded driver, thus, trying to have the same API. It >> supports extensions like Cypher or Gremlin, indexes with complex >> lookups using composition of Lucene fulltext queries, and >> transactions wrapped through the batch REST operation.
>> On Thu, Mar 15, 2012 at 15:38, James Thornton <james.thorn...@gmail.com> >> wrote:
>> > REST is usually fast enough, esp for a Web app's access patterns.
>> > Use Gremlin for server-side scripting to combine multiple HTTP requests >> > into one transactional request -- Bulbs/Python >> > (https://github.com/espeed/bulbs) was designed for this purpose and is >> very >> > Gremlin-centric.
>> > Bulbs was built with Flask in mind because Flask isn't tied to an ORM, >> but >> > it's generic and works with any Python Web framework.
>> > The Bulbs 0.3 docs are coming soon. Look at Ligthbulb >> > (https://github.com/espeed/lightbulb) for more examples -- it will be >> used >> > in the upcoming docs as an example app.
>> > - James
>> > On Thursday, March 15, 2012 1:10:31 PM UTC-6, Manav Goel wrote:
>> >> We are working in python and our webapp is almost beta launch ready.
>> >> We were planning on using neo4j before starting but due to some >> >> problems we had to move away from it.
>> >> Now situation is such that we can use neo4j again and the debate is >> >> python REST or Scala with embedded.
>> >> I am in favour that python REST is slow but not that slow that we need >> >> to port to entirely different language just for the sake of embedded >> >> and I also read when neo4j needs to be moved standalone on a separate >> >> server REST will come into play again.
On Thursday, March 15, 2012 3:10:31 PM UTC-4, Manav Goel wrote:
> We are working in python and our webapp is almost beta launch ready.
> We were planning on using neo4j before starting but due to some > problems we had to move away from it.
> Now situation is such that we can use neo4j again and the debate is > python REST or Scala with embedded.
> I am in favour that python REST is slow but not that slow that we need > to port to entirely different language just for the sake of embedded > and I also read when neo4j needs to be moved standalone on a separate > server REST will come into play again.
