...though there are perfectly good reasons to include business logic on the server as well (e.g. stored procedures, which Neo4J can support in its own way via server-side extensions).
-----Original Message----- From: user-boun...@lists.neo4j.org [mailto:user-boun...@lists.neo4j.org] On Behalf Of Jim Webber Sent: Friday, December 02, 2011 6:36 AM To: Neo4j user discussions Subject: Re: [Neo4j] Standalone server and transactions > > It is a long topic on itself: Where the business logic belongs to - the > server or the client. > > But the point is that far the most common use-case is to write the business > logic on the client, not on the server. > > The business logic on the server has already failed multiple times in the > history (think of stored procedures on the RDBMS). > > Server side logic works well when the DB is part of the app (e.g. embedded) > and server/client code is often indistinguishable. I don't believe that we are talking about business logic on the server - we're talking about data access logic (queries). Business logic binds to that data over the network - that the data is sourced through a plugin is an implementation detail. Jim _______________________________________________ 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
