Consider portability between system interface

             The interface between the various system a few years ago by many database companies linked to server data push or pull each other data, such as database systems are deployed into the network in the company,

And belong to the same network segment, data sources used to provide a view, a stored procedure performed by the job access, to set the job execution frequency control execution frequency. These years have passed between systems to

Interface more and more, synchronization job is more and more, more and more difficult to maintain.

            Now start thinking about upgrading your system or system migration to cloud the issue of third-party platform, the question came naturally, does our interface to access the public or to a public address,

Then use public addresses to link databases? So too unsafe, not the easy maintenance. Swollen do? Behind the new system or do not project this way to achieve synchronization, and are

Can be unified with the webservice systems, scheduling jobs, you can test into account with Quartz to do, or to write a dispatcher is required. Interface before the system would need to slowly

Improved over, so that later ported to the cloud platform system if it is a lot of convenience.

         So portability between system interfaces in the system design when we must consider carefully, not because of negligence or lazy cause problems for future maintenance.


Reproduced in: https: //www.cnblogs.com/kevinGao/p/4188715.html

Guess you like

Origin blog.csdn.net/weixin_33834679/article/details/93767165