|
|
The product was successfully launched. With the development of business, considering the cost and the quality of the manufacturer's equipment, the company chose similar equipment from another manufacturer. But the problem came. The data format of the new manufacturer was completely different from that of the previous manufacturer. In order to access the new equipment , their product architecture became as follows.
How to design IoT device access products? The business module has become fat and requires new business logic to connect to the new manufacturer's data API interface. What's even more wrong is that the field names on their front-end page are hard-coded Indonesia Telegram Number Data according to the previous device, which means that the front-end application also needs to be adapted according to different manufacturer types.
If it is manufacturer , it should follow the data format of manufacturer Display, if it is Manufacturer , display it according to the data format of Manufacturer After that, the company introduced new manufacturers, and then the development students were exploded - it was like artificially creating a code shit mountain! When a new manufacturer is introduced, firstly, the entire development chain from device data API docking to business logic processing to front-end page display needs to be modified accordingly; secondly, the entire business code contains a bunch of conditional judgments based on different manufacturers. ,
|
|
發表於 2024-3-12 14:47:59