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: Load a configuration file from the filesystem one time only. Load the configuration into our store (container) – one time only. Retain the configuration in the store such that it’s available in the app to get parameters throughout […]
