- 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.
推薦閱讀
- 計算機網絡與數據通信
- 信息通信網絡建設安全管理概要2
- Socket.IO Real-time Web Application Development
- 城域網與廣域網(第2版)
- 物聯網長距離無線通信技術應用與開發
- INSTANT KineticJS Starter
- Android UI Design
- 物聯網
- Intelligent Mobile Projects with TensorFlow
- 工業以太網技術:AFDX/TTE網絡原理、接口、互連與安全
- 網絡互聯技術(理論篇)
- 智能物聯安防視頻技術基礎與應用
- Architecting Data:Intensive Applications
- 企業網絡組建與維護項目式教程
- Learning IoT with Particle Photon and Electron