These services make sense when you need control over the lib because you have none over the application implementing the lib. Hiding information from developers should not be the reason to make configuration so complicated. One more service to be secured, maintained, monitored, etc. Should I be hitting yet another centralized service to get thisĮndpoints so no one is required to know the value?Ĭentralised remote configuration services are by any meaning one more failure point for which you must have a failover operation. Or provide with ports and adapters, so the consumer can adapt lib's configuration to its configuration solution. In consequence, this information is unlikely to end in any repository.Ī good and reasonable alternative would be making lib's code more parametrizable. This is a good way for the IT team to set sensible configurations (e.g passwords, seeds, tokens, URL, IPs, ports, etc) without sharing this information with you. Others are focused on supporting more execution environments over which we have no control. The last two are the ones we use in local env while coding and testing. Each source adds new entries to the configuration or replaces existing ones following last to arrive, win strategy. Config files in the file system (local or remote)īasically, the framework loads these sources in reverse order.Many support configuration overloading out of the box.Ī pattern of configuration overloading by source could be *: Option 2 is fairly common in today's projects, but it's because of the frameworks.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |