Fliggy: Server Development Series-System Architecture

 

This article mainly introduces the architecture of the distributed monitoring system of the company. First, let's talk about what this system is used for. Our system is a GIS monitoring system that monitors vehicles in real time. It can be combined with maps to know where the car is located in real time, in-Vehicle basic information, because of the listening and photographing functions. Its structure is as follows:

 

Because this system involves multiple different individual, the relationship between individual and individual is relatively small, and the only association is achieved through communication, in this way, the communication protocol becomes very important. In my opinion, the most important part of the communication system is the protocol. I don't know much about the hardware involved in the device, but it is the protocol that allows individuals on the three layers to develop independently and follow the protocol, here I will focus on the architecture of the servers in our system.

 

The server involves equipment, various monitoring systems (such as WebGIS and monitoring center GIS) and databases. For the performance and robustness of the entire system, our servers are divided into three subsystems: app server, Gateway server, and data server,

APP server: it can process various client connections and isolate the impact of various client conditions on the entire server.

Gateway server: The Gateway server is mainly used to connect devices. Different devices can convert the protocols of devices into internal protocols. The conversion here is very important.

Data Server: The Flying Pigeon book mainly writes app or gateway data to the database.

 

This is the architecture of our server. At last, it is divided into three subsystems. My understanding is as follows:

① Robustness: the external network environment is ever-changing. For internal networks, it can be considered that the local machine communicates with the local machine without many uncertainties. Divided into three sub-systems. A sub-system has a problem and can run without affecting other sub-systems.

② Performance: For three servers, we can deploy these three subsystems on three different machines, so that we can use the advantages of multiple machines to improve the performance of the entire system.

Flying Pigeon book: http://www.freeeim.com/