Apisecure, 14 & 15 March 2023 - Cherish Santoshi, Sr. Developer Relations Engineer at Orkes.
summary
API orchestration centralizes data transformation, runtime policies, RBAC and observability so distributed APIs become more resilient, secure and debuggable. The team uses Netflix Conductor, an open source, language-agnostic orchestrator, to run parallel and sequential workflows, visualize start/end times and pinpoint failures. Benchmark notes show up to a million workflows per month in real deployments. The built workflows handle legacy integration, retries and reroutes and demonstrably improve availability, scaling and incident diagnosis.
AI-written summary · about
chapters (20)
- 0:00API orchestration intro
- 1:07API architecture challenges
- 3:55What is API orchestration
- 5:00Key aspects of orchestration
- 6:46Data transformation in APIs
- 7:50Runtime security & resiliency
- 8:52Legacy system integration
- 10:13Authentication and role-based access control
- 11:17Observability in distributed APIs
- 12:00Orchestration tools like Conductor
- 14:47Orchestrator for security
- 16:13Defining resiliency
- 17:23Q&A debugging
- 18:06Debugging distributed APIs
- 19:31API orchestration tools Q&A
- 20:13Orchestration performance
- 23:22Speaker background
- 25:51Building dev community
- 29:42Bug bounty strategies
- 34:24Closing remarks
related talks
26mGrowing Pain: Scaling to 10K Workflows per Week
29mHas Everyone Forgotten Application Workflows in Kubernetes?
29mAPIs and Event Streaming Dualty
28mThink Backstage! Beyond Plugins
07h 08mAsyncAPI online conference | #asyncapiconf
28mPractical Microservices, Practical Whiskey
31mWriting Reliable, Scalable, Fault Oblivious Code On K8s the Easy Way
20mDemystifying Argo Workflows: An Architectural Deep Dive