Re: [Neo4j] REST API - always batch?
Dmytri, sounds like an interesting plan! I don't think there is anything directly that I can see, except a bug, https://github.com/neo4j/community/issues/113 with "\\" which you might watch our for, reported by Josh Adell. Let us know how it works out! Cheers, /peter neubauer GTalk: neubauer.peter Skype peter.neubauer Phone +46 704 106975 LinkedIn http://www.linkedin.com/in/neubauer Twitter http://twitter.com/peterneubauer brew install neo4j && neo4j start heroku addons:add neo4j On Thu, Dec 1, 2011 at 5:53 AM, Dmytrii Nagirniak wrote: > Hi, > > I wonder what the disadvantages would be if every request to the server would > always be a batch (even for simple GETs)? > > This would make it easier to use the API from the application. > > How bad is this idea? > > Cheers, > Dima > http://www.ApproachE.com > > > > > ___ > Neo4j mailing list > User@lists.neo4j.org > https://lists.neo4j.org/mailman/listinfo/user ___ Neo4j mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user
Re: [Neo4j] REST API - always batch?
Thanks Peter. I was asking because of the request to support batching in neography: https://github.com/maxdemarzi/neography/issues/16 I sounds like the "normal" API is obsolete then :) It encourages non-transactional operations. I think the batch-ing should be promoted a little bit more. Check the availability and place the reservation if something is still available is pretty hard to implement without it. Not sure if batching supports conditional operations though. Does it? Is there anything that would be impossible/slow etc to do with batching? I mean, there must be some drawbacks :) Cheers. On 01/12/2011, at 6:08 PM, Peter Neubauer wrote: > Dmytri, > sounds like an interesting plan! I don't think there is anything > directly that I can see, except a bug, > https://github.com/neo4j/community/issues/113 with "\\" which you > might watch our for, reported by Josh Adell. > > Let us know how it works out! > > Cheers, > > /peter neubauer > > GTalk: neubauer.peter > Skype peter.neubauer > Phone +46 704 106975 > LinkedIn http://www.linkedin.com/in/neubauer > Twitter http://twitter.com/peterneubauer > > brew install neo4j && neo4j start > heroku addons:add neo4j > > > > On Thu, Dec 1, 2011 at 5:53 AM, Dmytrii Nagirniak wrote: >> Hi, >> >> I wonder what the disadvantages would be if every request to the server >> would always be a batch (even for simple GETs)? >> >> This would make it easier to use the API from the application. >> >> How bad is this idea? >> >> Cheers, >> Dima >> http://www.ApproachE.com >> >> >> >> >> ___ >> Neo4j mailing list >> User@lists.neo4j.org >> https://lists.neo4j.org/mailman/listinfo/user > ___ > Neo4j mailing list > User@lists.neo4j.org > https://lists.neo4j.org/mailman/listinfo/user ___ Neo4j mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user
Re: [Neo4j] REST API - always batch?
I think especially for atomic create operations that will be solved by a GEOFF import plugin in the future. which allows for updates/insertions of subgraphs. https://github.com/nigelsmall/py2neo/wiki/GEOFF Michael Am 01.12.2011 um 09:03 schrieb Dmytrii Nagirniak: > Thanks Peter. > > I was asking because of the request to support batching in neography: > https://github.com/maxdemarzi/neography/issues/16 > > I sounds like the "normal" API is obsolete then :) > > It encourages non-transactional operations. I think the batch-ing should be > promoted a little bit more. > > Check the availability and place the reservation if something is still > available is pretty hard to implement without it. > Not sure if batching supports conditional operations though. Does it? > > Is there anything that would be impossible/slow etc to do with batching? > I mean, there must be some drawbacks :) > > Cheers. > > On 01/12/2011, at 6:08 PM, Peter Neubauer wrote: > >> Dmytri, >> sounds like an interesting plan! I don't think there is anything >> directly that I can see, except a bug, >> https://github.com/neo4j/community/issues/113 with "\\" which you >> might watch our for, reported by Josh Adell. >> >> Let us know how it works out! >> >> Cheers, >> >> /peter neubauer >> >> GTalk: neubauer.peter >> Skype peter.neubauer >> Phone +46 704 106975 >> LinkedIn http://www.linkedin.com/in/neubauer >> Twitter http://twitter.com/peterneubauer >> >> brew install neo4j && neo4j start >> heroku addons:add neo4j >> >> >> >> On Thu, Dec 1, 2011 at 5:53 AM, Dmytrii Nagirniak wrote: >>> Hi, >>> >>> I wonder what the disadvantages would be if every request to the server >>> would always be a batch (even for simple GETs)? >>> >>> This would make it easier to use the API from the application. >>> >>> How bad is this idea? >>> >>> Cheers, >>> Dima >>> http://www.ApproachE.com >>> >>> >>> >>> >>> ___ >>> Neo4j mailing list >>> User@lists.neo4j.org >>> https://lists.neo4j.org/mailman/listinfo/user >> ___ >> Neo4j mailing list >> User@lists.neo4j.org >> https://lists.neo4j.org/mailman/listinfo/user > > ___ > Neo4j mailing list > User@lists.neo4j.org > https://lists.neo4j.org/mailman/listinfo/user ___ Neo4j mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user
Re: [Neo4j] REST API - always batch?
On Thu, Dec 1, 2011 at 9:03 AM, Dmytrii Nagirniak wrote: > Thanks Peter. > > I was asking because of the request to support batching in neography: > https://github.com/maxdemarzi/neography/issues/16 > > I sounds like the "normal" API is obsolete then :) > > It encourages non-transactional operations. I think the batch-ing should > be promoted a little bit more. > > Check the availability and place the reservation if something is still > available is pretty hard to implement without it. > Not sure if batching supports conditional operations though. Does it? > > Is there anything that would be impossible/slow etc to do with batching? > I mean, there must be some drawbacks :) > There are a few reasons we aren't pushing the batch API as the primary way to work with REST. One is that it's a bit more complex to get started with, but the two primary reasons are these: 1. There are limits to how large the results can be from a batch API call. The batch API supports streaming deserialization of it's input, but output is still created as a giant string in memory. It is reasonably easy to hit the limits of how large the batch API results can be when you start batching requests. 2. We don't want it to be the primary API. We have lots of ideas for how we can improve the current REST API (add full transactional support, massively improve throughput and latency), and so we would rather go down that road. The batch API is a pragmatic solution to a big problem, but I don't think it is a good long-term path to take. /jake Cheers. > > On 01/12/2011, at 6:08 PM, Peter Neubauer wrote: > > > Dmytri, > > sounds like an interesting plan! I don't think there is anything > > directly that I can see, except a bug, > > https://github.com/neo4j/community/issues/113 with "\\" which you > > might watch our for, reported by Josh Adell. > > > > Let us know how it works out! > > > > Cheers, > > > > /peter neubauer > > > > GTalk: neubauer.peter > > Skype peter.neubauer > > Phone +46 704 106975 > > LinkedIn http://www.linkedin.com/in/neubauer > > Twitter http://twitter.com/peterneubauer > > > > brew install neo4j && neo4j start > > heroku addons:add neo4j > > > > > > > > On Thu, Dec 1, 2011 at 5:53 AM, Dmytrii Nagirniak > wrote: > >> Hi, > >> > >> I wonder what the disadvantages would be if every request to the server > would always be a batch (even for simple GETs)? > >> > >> This would make it easier to use the API from the application. > >> > >> How bad is this idea? > >> > >> Cheers, > >> Dima > >> http://www.ApproachE.com > >> > >> > >> > >> > >> ___ > >> Neo4j mailing list > >> User@lists.neo4j.org > >> https://lists.neo4j.org/mailman/listinfo/user > > ___ > > Neo4j mailing list > > User@lists.neo4j.org > > https://lists.neo4j.org/mailman/listinfo/user > > ___ > Neo4j mailing list > User@lists.neo4j.org > https://lists.neo4j.org/mailman/listinfo/user > -- Jacob Hansson Phone: +46 (0) 763503395 Twitter: @jakewins ___ Neo4j mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user
Re: [Neo4j] REST API - always batch?
To toss my two cents in, I had been thinking about moving my REST library to use only batches for all CRUID operations. I've been putting it off, and I will probably drop the idea for now based on Jake's response. Jacob Hansson-2 wrote > > 1. There are limits to how large the results can be from a batch API > call... > > 2. ...We have lots of ideas for how we > can improve the current REST API (add full transactional support, > massively > improve throughput and latency)... > Having real transactions via the REST API (a bit of an oxymoron?) would be most welcome. -- Josh PS, has anyone else used the acronym CRUID (Create Read Update Index Delete) to describe Neo4j operations? My other attempt was "ICRUD" but that sounds like the stuff you rub out of your eyes when you wake up in the morning. -- View this message in context: http://neo4j-community-discussions.438527.n3.nabble.com/Neo4j-REST-API-always-batch-tp3550568p3551739.html Sent from the Neo4j Community Discussions mailing list archive at Nabble.com. ___ Neo4j mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user
Re: [Neo4j] REST API - always batch?
iCrud sounds more like what Apple fans will be asking for this Christmas. On 1 Dec 2011 14:46, "jadell" wrote: > To toss my two cents in, I had been thinking about moving my REST library > to > use only batches for all CRUID operations. I've been putting it off, and I > will probably drop the idea for now based on Jake's response. > > > Jacob Hansson-2 wrote > > > > 1. There are limits to how large the results can be from a batch API > > call... > > > > 2. ...We have lots of ideas for how we > > can improve the current REST API (add full transactional support, > > massively > > improve throughput and latency)... > > > > Having real transactions via the REST API (a bit of an oxymoron?) would be > most welcome. > > -- Josh > > PS, has anyone else used the acronym CRUID (Create Read Update Index > Delete) > to describe Neo4j operations? My other attempt was "ICRUD" but that sounds > like the stuff you rub out of your eyes when you wake up in the morning. > > -- > View this message in context: > http://neo4j-community-discussions.438527.n3.nabble.com/Neo4j-REST-API-always-batch-tp3550568p3551739.html > Sent from the Neo4j Community Discussions mailing list archive at > Nabble.com. > ___ > Neo4j mailing list > User@lists.neo4j.org > https://lists.neo4j.org/mailman/listinfo/user > ___ Neo4j mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user
Re: [Neo4j] REST API - always batch?
> > 1. There are limits to how large the results can be from a batch API call. Just curious, what those limits are and what happens if you hit it? > 2. ... We have lots of ideas for how we > can improve the current REST API (add full transactional support, massively > improve throughput and latency), and so we would rather go down that road. > The batch API is a pragmatic solution to a big problem, but I don't think > it is a good long-term path to take. That is really interesting. Can you give a bit more details on the REST transaction API? Any estimations on this? ___ Neo4j mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user
