Skip to content

How To Centralize Your Web Application Settings And Decouple Your Code From Back-End Dependent Logic & Code

Notifications You must be signed in to change notification settings

AhmedTarekHasan/ApplicationSettingsAsAnAsset

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

4 Commits
 
 
 
 
 
 

Repository files navigation

Application Settings As An Asset

How To Centralize Your Web Application Settings and Decouple Your Code From Back-End Dependent Logic and Code


Every web application needs some business related settings to be set by the application user to fulfill his needs at certain time. These settings could change from time to time but they are still an asset for the application user and for sure for the application developer. Sometimes developers deal with settings as if they are some secondary things that should not take much attention. For sure they develop some sort of a methodology to manage it but they don't give it much thinking. I believe that settings should be treated in a much better way as they represent a very important prospective regarding the business needs and some technical needs, so, why waste this.


This article is a walkthrough which takes you from the early steps of writing the code up to its final form.


Related Links:


Authors:

About

How To Centralize Your Web Application Settings And Decouple Your Code From Back-End Dependent Logic & Code

Topics

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published