Depends how often you are getting new data. If its not too often, you could write directly to SQL. Otherwise writing in batches like you suggest could work too.
After looking at your post again, and depending on data volume, you might be ok with a purely SQL solution too (ie, finding nodes 1 or 2 steps away on a graph is easy in SQL if your adjacency data is all in the db).
By schema-less, do you mean that it's possible that every new record in the database could have a few attribute-values that no other record has, or that you simply don't know what your attributes are at this time but at some point you will know them all?
If by schemaless you mean the arbitrary name/attribute pairs, you could simply use SQL, with an "attribute" table with "name" and "value", and "nodeid" columns.
Comments
Depends how often you are getting new data. If its not too often, you could write directly to SQL. Otherwise writing in batches like you suggest could work too.
After looking at your post again, and depending on data volume, you might be ok with a purely SQL solution too (ie, finding nodes 1 or 2 steps away on a graph is easy in SQL if your adjacency data is all in the db).
Yes, that's true. But I still have a requirement for a schemaless db, so sql doesn't cut it.
By schema-less, do you mean that it's possible that every new record in the database could have a few attribute-values that no other record has, or that you simply don't know what your attributes are at this time but at some point you will know them all?
If by schemaless you mean the arbitrary name/attribute pairs, you could simply use SQL, with an "attribute" table with "name" and "value", and "nodeid" columns.