Breaking this out of the talk about deprecating REST traversals (
http://neo4j.org/forums/#nabble-td3460396).
So, I'm trying to understand the arguments pro and con *POSTing arbitrary
code to the server*, as well as *writing server plugins for the sake of
adding domain logic inside the database*. To be clear, I'm not debating
plugins that extend general server functionality, like spatial, gremlin,
cypher and so on.
It sounds to me like the main argument for both of these is "you use it to
build SOA by deploying code into the database". I think SOA is kick-ass,
but I'm not sure I understand why running your domain logic inside your
database is a good way to go about building SOA systems.
Is the SOA thing the main argument for supporting arbitrary code execution?
if answer is True:
*What are the arguments for doing SOA this way?*
else:
*What is the main argument for arbitrary code execution then?*
The reason I want this discussion is because I'm worried that there are
problems with this approach that will bite us later, and I want to know
that the arguments pro are worth that pain. I also think that a lot of the
arguments for arbitrary script execution are related to shortcomings in the
server and in Cypher, and I don't think hacking around those shortcomings
is a good solution.
--
Jacob Hansson
Phone: +46 (0) 763503395
Twitter: @jakewins
_______________________________________________
Neo4j mailing list
User@lists.neo4j.org
https://lists.neo4j.org/mailman/listinfo/user
