Puppet Labs just released PuppetDB an optional (for-now) component of their configuration management software. The supported backends are HSQLDB and Postgres. W

Puppet Labs just released PuppetDB an optional (for-now) component of their configuration management software. The supported backends are HSQLDB and Postgres. When asked why MySQL wasn't supported, the developers' response was "The short answer is performance. To effectively implement things we've got on our roadmap, we need things that (current) MySQL doesn't support: array types are critical for efficiently supporting things like parameter values, recursive query support is critical for fast graph traversal operations, things like INTERSECT are handy for query generation, and we rely on fast joins (MySQL's nested loop joins don't always cut it). It's much easier for us to support databases with these features than those that don't. For fairly divergent database targets, it becomes really hard to get the performance we want while simultaneously keeping our codebase manageable... We certainly didn't make this decision cavalierly; it was made after around a month of benchmarking various solutions ranging from traditional databases like PostgreSQL to document stores like MongoDB to KV stores such as Riak to graph databases like Neo4J. For Puppet's particular type of workload, with Puppet's volume of data, with Puppet's required durability and safety requirements...I maintain this was the best choice. " http://groups.google.com/group/puppet-users/browse_thread/thread/66b123570d54a47f http://groups.google.com/group/puppet-users/browse_thread/th...