Spotify 的车队管理（下）：声明式基础设施之路

May 3, 2023 Published by David Flemström, Principal Product Manager, and Alexander Buck, Senior Engineer

2023年5月3日，由首席产品经理David Flemström和高级工程师Alexander Buck发布

This is part 2 in our series on Fleet Management at Spotify and how we manage our software at scale. See also part 1 and part 3. 

这是我们关于Spotify Fleet Management的系列文章的第2部分，介绍了我们如何管理规模化的软件。请参见第1部分和第3部分。 

At Spotify, we adopted the declarative infrastructure paradigm to evolve our infrastructure platform’s configuration management and control plane approach, allowing us to manage hundreds of thousands of cloud resources across tens of thousands of different services at scale.

在 Spotify，我们采用了声明式基础架构范例来演进我们的基础架构平台的配置管理和控制平面方法，使我们能够在规模上管理数十万个云资源和数万个不同的服务。

A few years ago, Spotify underwent a transition from being entirely hosted in our own on-premise data centers to instead running on the Google Cloud Platform (GCP). As part of this transition, we employed a “lift and shift” model, where existing services, their architecture, and the relationships with the underlying infrastructure were mostly preserved.

几年前，Spotify从完全托管在我们自己的本地数据中心转变为在Google Cloud Platform（GCP）上运行。作为这一转变的一部分，我们采用了“提升和转移”模型，其中现有服务、它们的架构以及与底层基础架构的关系大多得到保留。

This meant that the particular infrastructure choices developers made in the cloud varied a lot depending on the use case and team. As we learned more about running in a cloud environment, our best practice recommendations also evolved with our learning. For example, while we were running on premises, it was considered best practice to host your own Apache Cassandra cluster, deliver messages via Apache Kafka, run custom Elasticsearch or PostgreSQL instances, or install Memcached on dedicated VMs. The cloud provides managed equivalents for all of these — Google Cloud Bigtable and Cloud Pub/Sub, or running Memcached on top of Kubernetes, for example. As a result, the infrastructure that had been created over the years started forming a long tail — snapshots in time of whatever was considered the best practice of its day, along with the mistakes ...