Andrew Stanton-Nurse @anurse
One of the "Factors" in cloud native applications states you should store your configuration and settings outside of your core application code. In this episode, Andrew gives us a run down on how the configuration options in .NET Core allows for layers of configurability and abstractions for your app.
- Configuration has come a long way in ASP.NET…no more XML files?
- By default .NET Core manages settings and configuration in an order of operations per se? Can you talk about that.
- Can we mix the various options of configuration options? ENV, JSON, INI etc?
- What about Environments?
- Now that we have a base of what’s “in the box”, what about getting these configurations out of our code base and externalizing these? As a practice of Cloud Native we want to manage these separately and not have them tied directly to the code base.
- What are the options?
- Security, Practices?
- Are there conventions we should be aware of that the framework follows?