The data of other people cannot be produced by myself. 4) Reuse existing wheels, share API or SDK (may not invent it yourself). 2. The way of data transmission The job function email list way of data transmission, as a product manager, I divide it into: interface transmission, middleware transmission, message transmission, etc. Scattered, such as: MQ (queue), HTTP interface, otter, job function email list file sharing transmission, etc. Each has a subdivided way and suitable scene. 1. Interface This is a traditional question-and-answer transmission method, which is a typical c/s interaction mode. Equivalent to a client and a server (
Note: the client or server here is relative to the job function email list provider and receiver of the data, not necessarily actual). At present, our commonly used http calls, java remote calls, and webserivces all belong to this method, but the difference is the difference between the transmission protocol and the message format. 1) The role of the interface Through the interface, I can call job function email list mature third-party functional plug-ins for my use (usually the API interface), or write specific interface codes according to actual needs to solve the problem of information transmission in specific occasions (generally referred to as the http interface).
For back-end product managers, the http interface has the most usage scenarios. For example, the company first launched the OA system, and job function email list then launched the order system. The order system needs to synchronize the personnel organization information of the OA system. Then a feasible approach is to create an interface for the OA system to request the job function email list order system to obtain the latest personnel structure information. This general solution description includes such information: creating interfaces, requesting interfaces, obtaining the latest information, etc.