Move from Monolith to Microservices has enabled improved scalability, increased resiliency, and faster time to market. The rise of Microservices also saw the rise of new microservice design patterns including Microservice Orchestration. Orchestration frameworks give you several ways to manage your microservice workflows (business processes) based on application workload. Depending on if you need long-running workflows or Short duration workflows or UI-centric App flows requiring multi-app orchestration, you may need to design your workflows differently. This talk will cover use cases and journey of the Netflix Content Ingestion and Evaluation platform in using Conductor as an orchestration service and some of the lessons learned along the way and some best practices you should follow while designing your workflows. Some of the specific topics/questions this talk will cover are: What design principles are you adopting while designing your workflows? Simplicity Consistency Availability Reliability Maintainability Extensibility Scalability Security Authentication Authorization Encryption Privacy - PII | PCI Performance Resiliency Testability Reproducibility Evolvability Manageability … Orchestration Systems Best Practices [color=#111111][size=2][font=Verdana, Arial, Helvetica, sans-serif][h2][/font][/size][/color][b][color=#111111][size=2][font=Verdana, Arial, Helvetica, sans-serif][url=https://drive.google.com/file/d/1nK5ZMeKIPOAqbXB9VrHWeHCMmLHlvvcD/view?usp=sharing]Slides[/url][/font][/size][/color][/b][color=#111111][size=2][font=Verdana, Arial, Helvetica, sans-serif][/h2][/font][/size][/color]