Good visualization! One thing: in scenario #7 I'd like the App to access the "User REST" directly in addition (or instead of) just "REST Servlet". Because that's what your app would do, go directly through that User REST interface. Would you agreee?
2010/10/25 Andreas Kollegger <andreas.kolleg...@neotechnology.com> > Great catch, we should definitely capture that one. Attached... > > > > > On Oct 25, 2010, at 4:41 PM, Jan Boonen wrote: > > > Having read the discussion about an in-memory version of neo4j for unit > > testing last week. I'd propose to add that scenario as well. As far as I > > understood it's almost the same scenario as #1, but I would be triggered > > faster to use neo4j when such a scenario was documented. > > > > Cheers, > > > > Jan > > > > On 25-10-2010 15:55, Andreas Kollegger wrote: > >> Hi all, > >> > >> I've been sketching out various deployment scenarios for Neo4j, and have > come up with the attached list of diagrams. Targeted for this next milestone > release is packaging up scenario #7 into a standalone server install, with a > bonus mechanism for adding extensions to the REST API. > >> > >> Does this set provide a decent base set of use cases? Are there more > elaborate or simply different scenarios you'd like to see supported? > >> > >> Cheers, > >> Andreas > >> > >> > >> > >> > >> > >> > >> > >> > >> _______________________________________________ > >> 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 > > -- Mattias Persson, [matt...@neotechnology.com] Hacker, Neo Technology www.neotechnology.com _______________________________________________ Neo4j mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user
