Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Apidays Paris 2023 - How API Fit to a Modern Enterprise Integration Platform, Pascal Gacina, CGI

apidays
December 29, 2023

Apidays Paris 2023 - How API Fit to a Modern Enterprise Integration Platform, Pascal Gacina, CGI

Apidays Paris 2023 - Software and APIs for Smart, Sustainable and Sovereign Societies
December 6, 7 & 8, 2023

How API Fit to a Modern Enterprise Integration Platform
Pascal Gacina, Vice President Consulting Expert at CGI

------

Check out our conferences at https://www.apidays.global/

Do you want to sponsor or talk at one of our conferences?
https://apidays.typeform.com/to/ILJeAaV8

Learn more on APIscene, the global media made by the community for the community:
https://www.apiscene.io

Explore the API ecosystem with the API Landscape:
https://apilandscape.apiscene.io/

apidays

December 29, 2023
Tweet

More Decks by apidays

Other Decks in Programming

Transcript

  1. Liberate your data & the potential of your applications allowing

    to innovate for your customers, employees and partners… Some insight on how to use API and API Management as part of your Integration Platform ! How API & API Management fit a modern Entreprise Integration Platform ? About our today talk…
  2. Enterprise Event & Integration Practice 6 years old practice covering

    more 35 clients (from all sector) +100 Members +85 Certifications 9,50 / 10 Client Satisfactions (2023) 95% Client's recommendations +30% Year to Year growth since our creation Same for the last 6 years 9,38 / 10 Technological Expertise (2023) 9,28 since our creation partnership lead Vice President Consulting Expert at CGI https://fr.linkedin.com/in/pascalgacina 26 Years of Experience Living in Montpellier (former Parisian) “Professionally born (1996) in the beginning Internet area“ What we do…
  3. Liberate your data & the potential of your applications allowing

    to innovate for your customers, employees and partners… Enterprise Integration Platform… “Usually” seen on our client IT landscape A classical stack… 1 1 ETL/ELT, driven by Data Teams (Business Intelligence focused (with “hot today topic”, DataPlatform, DataMesh, GenIA..), often linked with Data Streaming (Kafka…) 1 2 Micro-Services, driven by Applications Teams (Application Team, Digital Teams, R&D Teams…) 2 3 3 3 3 ESB/IPaaS including Queuing / EDA (and if they success  Service Mesh) generally led by Architecture/Integration/SOA Team 3 4 4 MFT, often driven by RUN/OPS Teams and B2B/EDI “diluted” on project level 4
  4. Liberate your data & the potential of your applications allowing

    to innovate for your customers, employees and partners… You may already have API usage… Due to our SaaS / Multi-Cloud strategy… “I WANT” API / API Management managing our integration (you could insert here every « actual buzzword »  ) ! What our clients wants…
  5. Liberate your data & the potential of your applications allowing

    to innovate for your customers, employees and partners… The reality… API usage… ...you already have… Micro-Service, often use a “tactical” API Gateway (you could find multiple API Gateway too (across different Applications/Digital Teams)) 1 1 2 2 2 2 2 API Integration elsewhere to… • ETL/ELT: for mass data replication with SaaS Application (example: Salesforces or e- commerce applications…) • ESB/iPaaS: a “Tactical answer” project led driven • Streaming: Could use API (based on applications capabilities) • MFT & B2B: as partners ecosystem is changing… 2
  6. Liberate your data & the potential of your applications allowing

    to innovate for your customers, employees and partners… …You must deal with our API Users expectation…. Ok why we paid for multiple API Gateway, I want to rationalize everything using one solution… …after assessment…
  7. Liberate your data & the potential of your applications allowing

    to innovate for your customers, employees and partners… …“expectation”… and regulation… North America Africa Oceania Asia Europe South America You have to deal with your legacy API landscape and regional regulation (GDPR in Europe, China, Russia….)… and all solution are not available worldwide (or managed internally)… 1 …but choice are often project led driven and linked with regulation requirements… Multiples vendors yes… Understand but how to ensure that each region follow the same API Standard and Rules ? … Federated Gateway, API Marketplace, API Security, APIOPS could be a solution…
  8. Liberate your data & the potential of your applications allowing

    to innovate for your customers, employees and partners… …but beware of “hidden” cost… Great so I could use regional API and use them to build new services and applications… …Understanding API Users needs…
  9. Liberate your data & the potential of your applications allowing

    to innovate for your customers, employees and partners… Inter-cloud “hidden cost”... North America Africa Oceania Asia Europe South America …ingress and egress cost must be considered… Inter-Cloud Cost… Wait the new subscription solution are implemented in Australia and WE WANT TO USE IT WORLDWIDE ! … do not forget API Customer expectation… Beware of inter-region latency… Pricing Applications “Inter-Cloud” (inbound and outbound) traffic fees (not linked only to your API subscription) $ $ $ $ $
  10. Liberate your data & the potential of your applications allowing

    to innovate for your customers, employees and partners… …you must thing “Platform” and API & API Management part of it. Not aside… But we how to manage different expectation including API & API Management needs ? …OK now, but how to manage API as part Integration Platform ?
  11. Liberate your data & the potential of your applications allowing

    to innovate for your customers, employees and partners… …include API in your Integration Platform… including all shareholders… But with Governance… API Portal & API Gateway should be included as a service inside the catalog and managed the same as other “legacy” integration… 1 1 1 Governance with all shareholders to manage their expectations 2 2 3 Governance without Observability is worthless you must be “Transparent”… 3 4 NEVER FORGET ABOUT SECURITY 4
  12. Liberate your data & the potential of your applications allowing

    to innovate for your customers, employees and partners… …your Enterprise Finance Solution linked with Sales and ERP program let’s see it… Nice we have a use case now let’s use our new Platform ! …now a typical Use Case…
  13. Liberate your data & the potential of your applications allowing

    to innovate for your customers, employees and partners… …Using APIOpsCycles approach… …an approach including all Shareholders What it that ? Stocks API • Update e-commerce stock for store-to-web sales • Update POS stocks for web- to-store sales • Update Global stocks • Update Stocks valorization API Teams Automatic stocks update and stocks financial valorization based on sales an Integration API allowing to update stocks and at the same time update financial stocks valorization 1 API consumer are internal project but could include “reseller, marketplace…” 2 It was an IT project driven by Business 3 RapidAPI was the main API Catalog 4 With Anaplan API we could have more “real- time” stock valorization update (optimizing financial forecast) Financial Business want to have by Stocks update detailed information… 5 https://www.apiopscycles.com/
  14. Liberate your data & the potential of your applications allowing

    to innovate for your customers, employees and partners… …User Stories were written, and implementation starts…
  15. Liberate your data & the potential of your applications allowing

    to innovate for your customers, employees and partners… …well SAP projects extract flat files so we decide to use Bulk API from Anaplan  We use Anaplan, it is a SaaS solution, we follow your guidance, but Finance Users do not have their metrics… …the limits…
  16. Liberate your data & the potential of your applications allowing

    to innovate for your customers, employees and partners… …Focus on Bulk API… Yes and No… Are Bulk API “real API” Anaplan Bulk API Documentation Yes as it provide OpenAPI Endpoint (Good documentation and provided service is clear) YES No from the project view because of Finance shareholders expectations… NO Understand but could we do it differently ? … yes, it was project led decision link to your SAP Project! “Reality are key to success” This should have been done differently and challenging the Design and Expectation…
  17. Liberate your data & the potential of your applications allowing

    to innovate for your customers, employees and partners… Takeover some “hints” TECHNICAL VALIDATION BUSINESS CANVAS Include all shareholders Do an early technical validation (check expectation vs “reality”) CHALLENGE DESIGN Challenge Design and Expectation for “maybe” not fail…. Quick check-list… Use API when you need “fresh” information between applications 1 Include API and API Management inside your Integration Platform (avoiding API sprawling and point-to-point direct integration) 2 NEVER FORGET THAT API could handle “EDA approach” (Webhook, a POST is a Business Event…) and ecosystem is moving (example : Gravitee) 3 NEVET FORGET TO CHECK PROJECT USAGE AND SUPPORT (avoiding expectations miss and incomprehension) 4
  18. © 2023 CGI inc. Confidentiel © 2023 CGI inc. 18

    WE API FOR YOU ! https://www.cgi.com/france/fr-fr/api-management