Architect the ConfigStore – Part 1

Let’s architect our configuration store. We’ll start with identifying what it’s purpose is and why it exists. We’ll look at it from a reusable mindset to ensure that it can accept any configuration, as long as it follows our defined structure. In Part 2, we’ll walk through developing the structure of our API in procedural format.

The intent of our store is:

1. Load a configuration file from the filesystem one time only.
2. Load the configuration into our store (container) – one time only.
3. Retain the configuration in the store such that it’s available in the app to get parameters throughout the entire web page request.
4. Get a specific configuration from the store.
5. Get a specific parameter from a configuration within the store.

Key concepts to remember as we design it:

• Our store is a container.
• It will have an API to expose the getters and setters.
• It doesn’t care what the specific configuration is, as long as each file has one element where the key is the unique storage key and the value is the configuration.