"Nothing"---8---distributed configuration system Database Design _ Distributed System notes

It is obviously unwise to manually configure the programs on each server in the cluster, and it is not possible to bother with the differences caused by the inconsistencies.

And in the event of a configuration change, you need one by one to make changes, but also trouble

The acquisition and loading of configuration content is incorporated as a feature plug-in into the program. It receives the change notification from the Configuration service management side as a message listener, removes the data files generated locally by the old configuration data, and loads the new data files and loads them into the program.

This creates two stores of data, one at the service management end and one in the application's server, and why not load into the program directly.

Because the server is likely to be offline, and the application is restarted, a local reservation is maintained to be offline for the server. Database design

Solution Sheet: Each solution represents a portfolio of profiles required for a range of services, and the configuration data for different programs cannot be shared, although it creates a certain amount of work, but does not cause problems due to differences in the configuration requirements between programs that are caused by shared configuration data changes.

Field type action Soluationid GUID scheme ID soluationname character Scheme name Soluationsimple character Scheme Introduction APPID GUID Program ID enable boolean type scheme is enabled Createtime Time type creation date CreateBy integer creator modifytime Time type modified date modifyby integer modifier isdelete boolean Delete application table

Field type action AppId GUID application ID AppName character program name AppTitle character program display name Createtime time type creation date CreateBy integer creator modifytime Time type modification Date Modi Fyby integer modifier isdelete boolean Delete
Component table: Make uniform changes to the configuration file table through component data when a major change occurs

field type action ID integer data Id appplusid GUID component ID appplusname character program component name Createtime time type creation date CreateBy integer creator modifytime Time type modified Date Mod Ifyby integer modifier isdelete boolean Delete
Profile table: The configuration file required by the program component, and the data for this table is only added without modification

field type action ID GUID ID Soluationid GUID configuration scheme solution ID appplusid GUID component Id Title character configuration display name content XML configuration Content version Integer edition number, modify once content Automatically add a new version enable Boolean type scheme whether the Createtime time type creation date is enabled CreateBy the integer creator stoptime time type deactivate date modifyby integer modified person configuration History table:

field type action ID integer ID Soluationid GUID configuration scenario Solution ID soluationversion Integer solution version number Mdsid GUID service profile Id version Integer service profile version number Createt IME Time type creation date CreateBy integer creator