Slide 1

Slide 1 text

API Orchestration to build resilient apps Cherish Santoshi Developer Relations Engineer at Orkes CherishSantoshi CherishSantoshi

Slide 2

Slide 2 text

Agenda Current API architectures What is Orchestration How does it help Tools and methodologies 1. 2. 3. 4.

Slide 3

Slide 3 text

Typical API Architecture On Premises Cloud Developer Services Developer Portal • Internal • External • Partner Management Services API Management Service Management Platform Management Security Services API & WS Security • Authentication • Authorization • Threat Protection • Data Privacy • PCIDSS Analytics Services API Analytics • Operational • Consumer • Business Customer’s BI Federation Single Sign-On Access Control Mobile Web Partners Services Social IoT Interaction Layer API & Service Gateway Micro Orchestration Mediation Transformation Traffic Management Traditional Integration Layer Service Mediation Messaging Connectivity Application Layer Business Rules Business Process Orchestration Service Orchestration Sense & Response Information Management layer

Slide 4

Slide 4 text

Orchestration layer Client Applications End users Security Layer Caching Layer Representation layer Backend Systems API Implementations Orchestration Layer

Slide 5

Slide 5 text

NoSQL Database Oracle Database MySQL Database InfluxDB Database Microservice 1 (Python) Microservice 2 (Java) Microservice 3 (Node.js) Microservice 4 (Go) Server Stub Server Stub Server Stub Server Stub API (Orchestrator) Client 2 Client 1 Client 3 Distributed APIs

Slide 6

Slide 6 text

What is API Orchestration API orchestration refers to the process of integrating and managing multiple APIs to perform a unified task and create a seamless user experience. API orchestration can involve splitting, merging, or routing data to different APIs, depending on the desired outcome.

Slide 7

Slide 7 text

How does an Orchestration layer help? Data Transformation Runtime management Integrating language systems Authentication and RBAC Observability and debugging in Distributed applications 1. 2. 3. 4. 5.

Slide 8

Slide 8 text

Data Transformation Not every request for data is delivered or received using a common format. Both the client and the server could need the data answers to be transmitted in a certain format, requiring data transformation to enable communication in a standard call format. Using its transformation capabilities, the orchestration layer can intervene to guarantee that payloads are prepared appropriately.

Slide 9

Slide 9 text

Runtime management The orchestration layer can intervene before requests reach your API backend by treating each component of your application as a collection of microservices. Regarding security, this has a lot of benefits (runtime policies checking for malicious code threats). As a result, protocols, data validation, and error handling/logging are standardised.

Slide 10

Slide 10 text

Integrating legacy system Language agnostic Orchestration platforms like Conductor can help you connect with your legacy systems. Mixing of API types, such as REST and SOAP, can lead to major headaches when trying to use multiple APIs together. In steps, the orchestration layer normalises the data structures. This manages the flow of data and lets you communicate with the most neglected APIs and microservices.

Slide 11

Slide 11 text

Role-based permissions systems can be deployed since the orchestration layer can handle the authentication flow between microservices. This enables you to grant chosen people that fit a particular role access to only specific data. Authentication and Role Based Access Control

Slide 12

Slide 12 text

Observability and Debugging

Slide 13

Slide 13 text

https://github.com/Netflix/conductor

Slide 14

Slide 14 text

OSS Traction Media & Entertainment Telco, Security, Networking Retail, Logistics, Supply Chain, Travel E-Commerce HealthCare, Insurance Platforms, Dev Experience, App Modernization, Cloud Migration Fintech, Banking, Real Estate, Mortgage

Slide 15

Slide 15 text

Built using Orkes playground https://play.orkes.io/execution/a7ff7499- b8db-11ed-beff-42a493a6d9e1

Slide 16

Slide 16 text

Using an API orchestrator Stateful Serverless Visualize Language Agnostic Seamless Scaling Hybrid & Multi Cloud Actionable Insights

Slide 17

Slide 17 text

1. Try building a workflow at https://play.orkes.io/ 2. Join the Netflix conductor OSS repo: github.com/Netflix/conductor 3. Join our community

Slide 18

Slide 18 text

Thanks for your time Questions!?