A general, non-Neo4J note about cloning production data for testing:
1) It's a really good idea from a testing perspective
2) It's sometimes a really bad idea from a security perspective.
3) Everything I say here may not apply to your environment, but
will apply to someone's environment eventually
if Neo4J continues to be more and more successful.
With respect to (2), the problems that can come up are things related to
the security of the test environment, and the sensitivity of the data in
the production environment.
For example, if you have personally identifiable or sensitive
information - names, addresses, social security numbers, bank account
information, medical information, and so on in your production
environment, one needs to be careful about who gets access to this data.
Normally when you have sensitive information it is a good idea to
restrict who has access to the data using access controls through the
application and through the database (if available). However, such
restrictions don't make sense in a test environment, because of the
nature of chasing bugs. As a result, the sensitive data may not be
properly protected in the test environment.
For relational databases, there are tools to make copies of your
production data while disguising the sensitive parts. For example,
replace the names with random names from the phonebook. Similarly for
social security numbers, etc.
This looks like this will become an opportunity for someone in the
future - to provide such tools for Neo4J and/or other graph databases.
--
Alan Robertson<
al...@unix.sh> - @OSSAlanR
"Openness is the foundation and preservative of friendship... Let me claim from you at all times your undisguised opinions." - William Wilberforce