...

• foo.configurations.collection.get,
• foo.configurations.item.get (put/post/delete)

Storage Layer

UPDATE  This part probably doesn't make much sense from a security standpoint - it put's us right back to where we started.  

TBD... Just because the configuration APIs are distributed doesn't mean the configuration information must be.  In the case of storage modules, they may choose to just store their configuration in postgres as doing so would probably require little effort.  For business logic modules, or modules which have specific needs (e.g. the configuration is sensitive and should be encrypted, etc.) could choose to use a central configuration module for storage.

Here's where it might make sense to pull in additional technologies that are better suited to these requirements.  See the Technologies section below.  Having a module that presents a common interface in front of these technologies which is used internally (i.e. intended to be called only by other modules, not directly by clients) is an option that provides flexibility and opens the door to many potential benefits.

...