On Fri, 2009-07-03 at 10:10 -0400, Sam Rowe wrote: > If attention is being paid to this section of the code, would any > consideration be made to moving away from RoR/RDBMS toward something > more suited to the task? Or even just augmenting the available > back-ends?
That's our eldorado :-) But it isn't as easy as it sounds first, if you look to how puppet uses the database for collection, and storeconfigs. Then there's the issue of finding the proper storage engine. > It seems like using an RDBMS for this data not only doesn't benefit > from RDBMS features, but also makes it harder to store and retrieve > it. Would something like Tokyo Cabinet be a better fit? I didn't know Tokyo Cabinet, but the main issue with all key=value storage subsystem will be to adapt the collection query (currently rails only as pointed Luke) to something more versatile. I mean, when you write: File <<| tag== myfile |>> You need to be able to find the correct resource, so you have to create some special indices to map resources tags to resources, and it has to be done by hand. You need clever tricks to say that the key tag_myfile is pointing to a resource keyed by it's Type[title] string. Then perform a second look-up to look-up the resource itself. Basically what is cumbersome is mapping the complex storeconfigs namespace to a 1D system... > Of course you might say "It's not hard for me, RoR does it for me!" > but we've had other uses for our storedconfigs database that weren't > exactly RoR-friendly. Can you share with us your other usage patterns? -- Brice Figureau My Blog: http://www.masterzen.fr/ --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
