Portability considerations for interfaces between systems

In previous years, the interface between the company's various systems was mostly through database link server to push data or pull data between each other, because the database of these systems are deployed in the company to the intranet,

and belong to the same network segment, use the view to provide the data source, execute the stored procedure fetch number through the job, set the job to the frequency of execution to control how often. These years have passed, between systems to

More and more interfaces, synchronous operation is more and more, it is more and more difficult to maintain.

Now it's time to start thinking about upgrading the system or porting the system to a third-party cloud platform, and it's natural that our interface access or public address

Then use the public address to link the database? This is too unsafe, it is not easy to maintain. Do you have a swollen handle? New systems or projects in the future do not use this method to achieve synchronization, are

Can be unified with webservice to the system, job scheduling can be quartz to do, or write a scheduler itself. The interface of the previous system needs to be slowly

Improved, so that after the system is ported to the cloud platform is much easier.

Therefore, the portability of the system between the system design should be considered clearly, not because of a momentary negligence or lazy for future maintenance cause hidden trouble.

Portability considerations for interfaces between systems