-
Notifications
You must be signed in to change notification settings - Fork 445
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
3 changed files
with
8 additions
and
4 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1 @@ | ||
# FinOps 成本管控实践 |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,9 +1,11 @@ | ||
# 架构的演进 | ||
# 上云 | ||
|
||
这几年架构的演变从面向服务(Service-Oriented),到微服务(Microservices),到服务网格(Service Mesh),到无服务(Serverless)微函数, 技术组织上呈现出“从大到小”的发展趋势。 | ||
我第一次听到 `云原生` 这个词大概在 2017 年,CNCF 刚在国内始露苗头,一些技术论坛会讲一些云原生十二要素、声明式API、观测技术等话题,对第一次接触 `云原生`(Cloud Native)的我而言,这些都是一群很抽象的概念。当时云原生的核心还是:微服务 + DevOps + 容器化,而这些明明是一些很常见的开发技术,为什么 Google、CoreOS、RedHat 等等技术标杆型企业都纷纷高调宣扬拥抱云原生,而我却没有理解它,云原生让我产生了一种很强的挫败心理。 | ||
|
||
架构演变最重要的驱动力,或者说这种“从大到小”趋势的最根本的驱动力,始终都是为了方便某个服务能够顺利地“死去”与“重生”而设计的,个体服务的生死更迭,是关系到整个系统能否可靠续存的关键因素。 | ||
后来因为关注 Docker 和 Google 之间的八卦纷争,让我逐渐对容器技术、编排技术产生浓厚的兴趣,而在这一阶段,CNCF 也开始逐渐壮大,Istio、Knative 等等一系列开源方案频繁地面世,让 Service Mesh、Serverless 这些革新思想,真正进入了解决生产中的各类问题,可落地实施的阶段。 | ||
|
||
其次,企业降本增效、对上云的需要, | ||
一众云计算服务商(阿里云、AWS、Azure...)也开始统一行业标准,对各类资源进行规范封装,并提供完善的 PaaS 层供业务层对接,这个时候,充分利用云的特性,助力企业商业价值增长,对于理解云原生、拥抱云原生就是最强的驱动力。 | ||
|
||
|
||
只要整体架构设计有良好的自动化淘汰、重建、熔断措施,在系统外部来观察,整体上仍然有可能表现出稳定和健壮的服务能力。 | ||
|