We’re seeing more teams explore multi-architecture strategies — especially combining ARM (like AWS Graviton) and x64 workloads — to optimize for cost, performance, and infrastructure flexibility.
But deployment at scale is messy. CI/CD workflows get more complex, tooling becomes inconsistent, and governance often lags behind.
Curious how others are handling this:
• Are you running multi-arch builds in CI/CD?
• How do you manage compatibility, testing, or manifest handling?
• Are security, compliance, or org structure slowing you down?
We’re seeing more teams explore multi-architecture strategies — especially combining ARM (like AWS Graviton) and x64 workloads — to optimize for cost, performance, and infrastructure flexibility.
But deployment at scale is messy. CI/CD workflows get more complex, tooling becomes inconsistent, and governance often lags behind.
Curious how others are handling this:
• Are you running multi-arch builds in CI/CD? • How do you manage compatibility, testing, or manifest handling? • Are security, compliance, or org structure slowing you down?
We recently published a piece on the business case and real-world use cases here: https://caepe.sh/multi-architecture-arm-x64-at-scale/
Would love to hear how others are navigating this — especially at scale.
Thanks!