tamim2369@gmail 發表於 14:30:13

With the development of business, considering

There was only one manufacturer of IoT equipment selected for their products, so the product design was not considered too much. The purpose of development was to go online as soon as possible, so the following product architecture was designed. How to design IoT device access products? The structure is very simple, and the implementation is indeed very fast. 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 FR Numbers completely different from that of the previous manufacturer. In order to access the new equipment , their product architecture became as follows.


https://lh7-us.googleusercontent.com/c_QrObcvfU65-54dw59tT9Pv1BthZZNj5bRMvObeGXMHtz3ptcSmd5ucOE3mZr_2jnx7bacFvgJLNyIlCD7xLKSB4uR_qI8Ojf3O5jh7agmygg_4V1jeAwt1UPXKstvtQ1ILd8MbBe2_qib9




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 according to the previous device, which means that the front-end application also needs to be adapted according to different manufacturer types.

頁: [1]
查看完整版本: With the development of business, considering

一粒米 | 中興米 | 論壇美工 | 設計 抗ddos | 天堂私服 | ddos | ddos | 防ddos | 防禦ddos | 防ddos主機 | 天堂美工 | 設計 防ddos主機 | 抗ddos主機 | 抗ddos | 抗ddos主機 | 抗攻擊論壇 | 天堂自動贊助 | 免費論壇 | 天堂私服 | 天堂123 | 台南清潔 | 天堂 | 天堂私服 | 免費論壇申請 | 抗ddos | 虛擬主機 | 實體主機 | vps | 網域註冊 | 抗攻擊遊戲主機 | ddos |