Replacing Netflix Conductor with AWS Step Functions: What We Learned

This article provides a comprehensive guide for migrating from Netflix Conductor to AWS Step Functions, highlighting cost savings, improved reliability, and enhanced scalability.

• Netflix discontinued Conductor development in December 2023; migration offers 40-60% infrastructure cost reduction
• Step Functions provides native integration with 220+ AWS services versus custom HTTP workers in Conductor
• Migration strategy includes four phases: assessment, pilot, bulk migration, and production cutover over 3-4 months
• Key differences: Step Functions uses explicit data passing (InputPath/OutputPath) versus Conductor's global workflow context
• Media processing use case demonstrates event-driven workflows using S3, EventBridge, Lambda, and MediaConvert
• Reference implementation available on GitHub with TypeScript/AWS CDK examples and automated migration tools
• Mid-size deployment (1,000 workflows/month) costs ~$200/month on Step Functions versus $1,200+ for self-hosted Conductor
• Phased cutover approach minimizes disruption; gradual traffic shifting from 10% to 100% recommended

The guide emphasizes security best practices, provides construct mapping tables, and includes cleanup procedures for reference implementations.