On 24.05.2011 18:27, Luke Kanies wrote:
On May 24, 2011, at 1:31 AM, R.I.Pienaar wrote:
We looked in storing the graphs in some document database after
post processing them into a more palatable format and this seemed
to work ok but it does feel like a hack.
How did you pick your documents - catalogs containing resources and
edges, or all broken out separately? That seems the biggest
challenge to the document db - you either get a huge number of
objects to update each time, or you have a very large recursive
document that you're trying to query.
From my - limited - understanding of document databases, Catalogs and
Reports would be the proper documents, and the database would provide
something like map/reduce or custom indices (e.g. RavenDB) to make
database-wide queries (e.g. for collecting).
Alternatively, I can imagine keeping the exported resources in manually
maintained "binning" documents, which can then be queried. But that
indeed sounds like a hack to emulate a map/reduce functionality.
Best Regards, David
--
dasz.at OG Tel: +43 (0)664 2602670 Web: http://dasz.at
Wien UID: ATU64260999
FB-Nr.: FN 309285 g FB-Gericht: Wien
--
You received this message because you are subscribed to the Google Groups "Puppet
Developers" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/puppet-dev?hl=en.
