- Hands-On Microservices with Kotlin
- Juan Antonio Medina Iglesias
- 150字
- 2021-06-30 19:10:41
Isolation
A microservice should be physically and/or logically isolated from the infrastructure that uses the systems that it depends on. If we use a database, it must be our database, if we are running in a server, it should be in our server, and so on. With this, we guarantee that nothing external is affecting us and neither are we affecting anything external.
This will help from deployments to performance or monitoring, or even in building our continuous delivery pipeline. It will facilitate how we can be controlled and scaled independently, and will help the ops functions within our team to manage our microservices.
We should move away from the days when a failure in some parts of the architecture was affecting others. Containers are one of the key architectures to effectively archive this principle. We will learn more about this in the Cloud Native microservices section of this chapter.
- Android Wearable Programming
- Boost.Asio C++ Network Programming(Second Edition)
- 多媒體CAI課件設計與制作導論(第二版)
- Learning ArcGIS Pro 2
- Vue.js前端開發基礎與項目實戰
- AngularJS深度剖析與最佳實踐
- Instant RubyMotion App Development
- Drupal 8 Configuration Management
- 小學生C++創意編程(視頻教學版)
- Visual C++開發入行真功夫
- 西門子S7-200 SMART PLC編程從入門到實踐
- Solr Cookbook(Third Edition)
- Mobile Device Exploitation Cookbook
- ASP.NET程序開發范例寶典
- 硬件產品設計與開發:從原型到交付