Learn Cloud-Native .NET: Core Configuration Fundamentals with Steeltoe

How do you avoid a messy jumble of configuration management? First, you can rule out holding settings internally to the app. Hard coding values in a compiled artifact limits almost everything about an application’s ability to scale. Attaching a .config file to each instance of the application is also not reasonable. (Yes, your externalized config values from the artifact.) But you’re no better off with managing and updating things. This class will visit the Microsoft.Extensions.Configuration package and the many options it offers .NET Core developers. We’ll cover everything from using the default providers (and what’s going on under the covers) to custom providers implemented in Steeltoe. There are many stops in between where developers can achieve the best mix of business requirements and technical needs. Attend this class to learn the following: ● How to use external configurations with Spring Config using Steeltoe ● Best practices for externalizing configuration ● How to get the most from Spring Config without adding complexity