Is HTTP as a protocol the problem? Maybe, it does have some advantages 
though.

I think we all agree the REST API is not finished yet.  
We talked last week about Batch operations as a poor-man's replacement for 
Transactions and the concerns that brought up.

I think the REST API will get there eventually... or (since it had a short 
brush with death two months ago)  be replaced with a full Cypher language 
with data operations (INSERT, UPDATE, DELETE SQL equivalents)

In the mean time, my solution has been Polyglot Persistence using 
ActiveRecord callbacks.  

  after_create :create_node

  def create_node
    if self.valid?
      self.node = $neo.create_node("identity_id" => 
self.id)["self"].split("/).last 
    self.save 
  end 

  after_save :create_relationship

  def create_relationship
    from = self.grantor.node
    to = self.requester.node
    $neo.create_relationship("vouched", from, to) 
  end 

You don't have to limit yourself to one database.  
Chances are you'll need Redis anyway, so you might as well think in terms of 
multiple storage units from the beginning. 

_______________________________________________
NOTICE: THIS MAILING LIST IS BEING SWITCHED TO GOOGLE GROUPS, please register 
and consider posting at https://groups.google.com/forum/#!forum/neo4j

Neo4j mailing list
User@lists.neo4j.org
https://lists.neo4j.org/mailman/listinfo/user

Reply via email to