In the field of computer technology, there is a "Moore's Law", which was discovered by Intel Honorary Chairman Gordon Moore after long-term observation. It means that the number of transistors that can be accommodated on an integrated circuit will double approximately every 18 months. . Isn't this true in the software field? Especially to some extent. When I first went to college in 1992, I was faced with 8088 machines. Program development was based on the command line interface Turbo C2.0, Foxbase database and other "earth guns", and concepts such as network programming, concurrent processing, and transaction control. Still unheard of. When I was doing my graduation project in my senior year in 1996, one of our teachers named Teng led the graduation project and introduced us to program development in the client/server model. The tool used was Sybase/PowerBuilder. Now even the original version of PowerBuilder is no longer available. Forgot, I left school before I could understand the development concept of client/server model. After graduating to the IRS, I saw the LAN-based collection software, which used NetWare file server and Foxpro2.5. In order to solve concurrent processing, there were a lot of codes for locking and unlocking tables or records in the program. In order to solve the problem of a certain table, Programmers racked their brains whether to open exclusively or sharedly. In the late 1990s, a large number of C/S applications appeared in the workplace, such as VB+SQL Server mode, PowerBuilder Sybase mode, Delphi+MS SqlServer mode, etc. Under the C/S method, programmers have gained great benefits. Free, you don’t have to worry about the locking and unlocking of the database, but you need to consider issues such as transaction processing, two-phase commit and rollback, and data consistency. Later, with the boom of the Internet, B/S architecture application systems appeared, and CGI, PHP, ASP, and JSP technologies gradually became popular. However, both the Client/Server and Browser/Server architectures have a fatal flaw, that is, they work independently and cannot get rid of the bad luck of "information islands" and cannot realize the integration of distributed systems. To give the simplest example, entrusting a certain The software company developed a system for purchase, sale and inventory management and inventory management, and also purchased a set of financial software, both of which have a C/S structure. There is no way for the two systems to communicate, and accounting vouchers need to be entered manually. In order to solve this problem, technicians usually use the method of exchanging data files, such as using standardized TXT files with equal width, writing data export files that can be recognized by the data input system for the data output system, and then manually importing them by the data input system. This method has poor real-time performance and data is easily lost during the exchange process. Some simply write Socket programs for communication [Figure 1]. For example, the Golden Tax Project invoice cross-audit system uses this method for communication and integration between the audit systems of the General Administration, provincial bureaus, and municipal bureaus.
Expand
