- Microservice Patterns and Best Practices
- Vinicius Feitosa Pacheco
- 105字
- 2021-06-30 19:02:57
Fail alert tools
Just as we prepare our product to be successful, we must also prepare for failures. There is nothing worse in microservices than silent errors. Receiving faulty alerts as soon as possible is critical, which is considered to be a healthy microservices ecosystem.
There are at least four major points of failure when it comes to microservices. If these points are covered, we can say that about 70% of the application is safe. These points are as follows:
- Performance
- Build
- Components
- Implementation failures
Let's understand what each of these risk points are and how we can receive failure alerts as soon as possible.
推薦閱讀
- 智慧城市:大數(shù)據(jù)、互聯(lián)網(wǎng)時(shí)代的城市治理(第4版)
- Web安全防護(hù)指南:基礎(chǔ)篇
- Cisco OSPF命令與配置手冊
- SOA用戶指南
- SEO 20日
- 計(jì)算機(jī)網(wǎng)絡(luò)與數(shù)據(jù)通信
- 計(jì)算機(jī)網(wǎng)絡(luò)與通信(第2版)
- C/C++串口通信:典型應(yīng)用實(shí)例編程實(shí)踐
- 光纖通信系統(tǒng)與網(wǎng)絡(luò)(修訂版)
- 網(wǎng)絡(luò)環(huán)境中基于用戶視角的信息質(zhì)量評價(jià)研究
- 4G小基站系統(tǒng)原理、組網(wǎng)及應(yīng)用
- 高級網(wǎng)絡(luò)技術(shù)
- 深入理解OpenStack Neutron
- 局域網(wǎng)組成實(shí)踐
- 云工廠:開啟中國制造云時(shí)代