Documents
Adobe's Reference Architecture
Adobe's Reference Architecture
Type
Document
Status
Published
Created
Oct 8, 2025
Updated
Oct 14, 2025

Adobe's reference architecture for scalable service delivery, as documented on architecture.cncf.io, is built on a cell-based pattern called Flex-in-a-box (FiaB). This architecture leverages several key CNCF projects to provide a robust, scalable, and developer-friendly internal platform. This guide outlines the essential CNCF projects, their roles in the architecture, and recommended CNCF and Linux Foundation training resources for technical teams.


Core CNCF Projects in Adobe's Reference Architecture#

Kubernetes (Graduated)#

Kubernetes is the foundational orchestration platform for Adobe's Internal Developer Platform. It manages containerized workloads and underpins the Flex Hub and Flexbox clusters, enabling horizontal scaling and multi-cluster management. All major workloads, CI/CD pipelines, and developer environments run on Kubernetes clusters.

Training Recommendations:

Helm (Graduated)#

Helm is used as the package manager for Kubernetes, abstracting deployment complexity and managing dependencies. In Adobe's architecture, Helm automates the deployment of Flexbox components and enables repeatable, consistent environment setups.

Training Recommendations:

Argo Project Suite (Graduated)#

Adobe uses the full Argo suite to implement GitOps-based CI/CD pipelines and advanced deployment strategies:

  • Argo CD: Provides declarative GitOps continuous delivery, synchronizing application state from Git to Kubernetes clusters.
  • Argo Workflows: Orchestrates complex CI/CD pipelines as Kubernetes-native workflows.
  • Argo Events: Enables event-driven automation, triggering workflows and deployments based on external events.
  • Argo Rollouts: Implements advanced deployment strategies such as canary and blue-green deployments.

These tools are central to the Flex platform's automation, lifecycle management, and service relocation capabilities.

Training Recommendations:

Backstage (Incubating)#

Backstage serves as the unified internal developer portal, providing standardized golden templates, service catalogs, and a single pane of glass for managing the application lifecycle. It integrates with CI/CD pipelines and infrastructure provisioning, streamlining developer onboarding and productivity.

Training Recommendations:


Architectural Roles and Integration Points#

Flex Hub and Flexboxes are Kubernetes clusters managed via Helm and Argo, supporting horizontal scaling and service relocation. The GitOps lifecycle is automated by Argo CD and Workflows, handling application delivery, infrastructure provisioning, and Flexbox lifecycle management. Argo Events and custom components (Redirector, Relocator) enable dynamic routing and zero-downtime service moves. Backstage provides a unified portal for bootstrapping, managing, and monitoring services, integrating with the underlying GitOps workflows.


For teams implementing Adobe's reference architecture, the following learning paths and certifications are recommended:

Platform Engineers and SREs should focus on Kubernetes administration (CKA), Helm, Argo CD, and GitOps practices. Application Developers should emphasize Kubernetes application development (CKAD), Helm, and Backstage usage. DevOps and CI/CD Engineers should specialize in the Argo suite, GitOps workflows, and advanced deployment strategies.

General Cloud Native Certifications:


Additional Resources#

This study guide provides a roadmap for technical teams to build expertise in the CNCF projects critical to implementing Adobe's scalable, GitOps-driven internal platform architecture.