I'm building an application where queries will fall reasonably distinctly into record retrieval and graph queries. I'd ideally like to store all of my data in a single Neo4J instance, but I'm concerned about scalability and ease of redeployment when we push updated software. SQL and document databases generally have compact network APIs that a JDBC (or equivalent) driver can use to execute a query and return the data in a compact, preparsed format, but it's my understanding that all queries to an external Neo4J instance go through the JSON-based API, requiring serialization and deserialization on both ends, as well as limiting the fancy features that the SDN AspectJ mode offers.
My initial thought had been to simply run the application backend on large servers with an embedded HA setup, but further examination of the deployment process has led me to conclude that this won't support a rapid, reliable upgrade cycle, since it will be too expensive to bounce the embedded instances. I remember that there was discussion of development of a more efficient network API for accessing external instances using the Java API and SDN; is this something that's on the roadmap? -- You received this message because you are subscribed to the Google Groups "Neo4j" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
