- Python Microservices Development
- Tarek Ziadé
- 211字
- 2021-07-02 18:54:18
Smaller projects
The second benefit is breaking the complexity of the project. When you add a feature to an application such as PDF reporting, even if you do it cleanly, you make the base code bigger, more complicated, and sometimes, slower. Building that feature in a separate application avoids this problem, and makes it easier to write it with whatever tools you want. You can refactor it often, shorten your release cycles, and stay on top of things. The growth of the application remains under your control.
Dealing with a smaller project also reduces risks when improving the application: if a team wants to try out the latest programming language or framework, they can iterate quickly on a prototype that implements the same microservice API, try it out, and decide whether or not to stick with it.
One real-life example in mind is the Firefox Sync storage microservice. There are currently some experiments to switch from the current Python + MySQL implementation to a Go-based one, which stores users' data in standalone SQLite databases. That prototype is highly experimental, but since we have isolated the storage feature in a microservice with a well-defined HTTP API, it's easy enough to give it a try with a small subset of the user base.
- Web程序設計及應用
- 從零開始構建企業級RAG系統
- Java語言程序設計
- Visual Basic編程:從基礎到實踐(第2版)
- PHP基礎案例教程
- Web Development with Django Cookbook
- AIRAndroid應用開發實戰
- aelf區塊鏈應用架構指南
- Python Network Programming Cookbook(Second Edition)
- Teaching with Google Classroom
- 軟件供應鏈安全:源代碼缺陷實例剖析
- UML2面向對象分析與設計(第2版)
- 大學計算機基礎實訓教程
- Visual Basic程序設計實驗指導及考試指南
- Drupal 8 Development Cookbook(Second Edition)