原书出处
Cloud Native Transformation
03 Chapter 3. What’s the Pattern? Architecture, Pattern Languages, and Design
This is because there are times where cloud native complexity is simply not called for. Highly stable and proficient systems that require little change or updating, for example, make for ideal monoliths and should be run as such. Attempting to split such a system into containerized microservices would be an interesting thought experiment, costing time and resources to do while ultimately producing little functional improvement. “Monolith” is not a dirty
原书定位详情
来源:a19c7933-4eda-4176-aebd-30fe7e1ad292
正文位置:extracted/Cloud Native Transformation/_epub-src/OEBPS/ch03.xhtml
EPUB SHA-256:6b5b7e9c3ecb3038152cdae7fa650179aacca16b684702c8f9f8ecb10e406565