Migrating to Kubernetes within 12 months, Figma transitioned from AWS ECS to EKS to enhance service reliability, scalability, and developer experience. The move facilitated the adoption of open-source technology, improved cost efficiency through node auto-scaling, and strengthened the platform's resilience with a three-cluster setup. The migration was meticulously scoped to avoid unnecessary complexity and executed with principles ensuring minimal disruption. Post-migration, the focus is on refining tooling and exploring new improvements like service mesh offerings and aligned logging pipelines.
Table of contents
On Figma’s compute platformScoping the migrationPerforming the migration safelyOur migrationWhat’s nextSort: