An overview of the

This week, I successively carried out the docking work of two business systems. Although I was not directly responsible for the development, I also spent a lot of energy. Fortunately, the progress was in line with expectations.

False assumptions about docking

1. When I contacted the technical personnel to communicate with them about the details of the connection for several times, they were confused. Who are you and what do you want to contact me for?

2. The technical personnel in charge of the docking have the technical ability required for the docking. Once, I communicated with a peer about the acquisition of system monitoring information and needed to obtain the underlying hardware information, so I needed to use THE STMP protocol. I sent the test and development materials related to STMP to the past, and they were also very helpful. After several twists and turns, they finally passed, but the progress was far behind expectations.

3. To connect the very willing to completed the work This also encountered many times, especially in the industry, is always for us to connect the calls with ignore, finally to coordinate their customers superior work units to the docking, the result is very simple and docking drag for a very long time, to make our users is very helpless and collapse.

The above problems are not technical level, in connection with this matter, technology is often not the main.

Docking point

  1. After the docking has entered the substantive stage, the two sides must bring technical personnel to communicate and establish contact groups, otherwise the two sides have no less boast, but the docking work has been delayed
  2. Contact and consult as soon as possible. If you have any questions, you must raise them
  3. Do the docking work in advance, most people like to do multiple choice, so before docking to do research, it is best to get a few sets of docking scheme, the other side a look at the ready-made scheme, as long as it is not too outrageous will be adopted, so that the development behind the initiative
  4. The most important thing is to have a process for alignment and interface document publishing, in the form of email and validation
  5. Don’t rely too much on documentation, and if you do have documentation, it’s best to check it frequently during development
  6. Establish test conditions as early as possible. Stubs are 10,000 times better than none
  7. Interface design must be careful, as little as possible to know the other side of the system, Restful can not use RPC or middleware, shared database can not use what
  8. If you have to use strong coupling technologies like WebService, separate the docking parts

Some good information about interface design

  • Opensource.zalando.com/restful-api…
  • www.infoq.com/presentatio…
  • www.vinaysahni.com/best-practi…
  • Betimdrenica.wordpress.com/2015/03/09/…
  • Github.com/interagent/…
  • Github.com/Microsoft/a…

Most of the information above is from geek Time’s Wind in the Left Ear column.