API Governance – Modern API solutions in a digitalized world
•Download as PPTX, PDF•
0 likes•440 views
The document discusses API governance and modern API solutions in a digital world. It notes that nearly 40% of US enterprises will adopt API management solutions by 2020, with the US API management market growing over fourfold from $140 million in 2014 to $660 million. The document presents scenarios for how APIs can support new mobile apps and digital transformation, and emphasizes that information is a key asset and APIs can be used to get and push data. It recommends taking a united front to API governance and recaps the presentation on experience, system and process layers for APIs.
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (11)
Similar to API Governance – Modern API solutions in a digitalized world
Similar to API Governance – Modern API solutions in a digitalized world (20)
More from BizTalk360
More from BizTalk360 (20)
Recently uploaded
Recently uploaded (20)
API Governance – Modern API solutions in a digitalized world
- 1. API Governance – Modern API solutions in a digitalized world Mattias Lögdberg https://se.linkedin.com/in/logdberg
- 3. Mattias Lögdberg Solution Architect Azure Specialist Azure Advisor & Insider MLogdberg MLogdberg https://se.linkedin.com/in/logdberg
- 6. Source: Gartner “Market Guide for Hybrid Integration Platform-Enabling Technologies,” by Elizabeth Golluscio, Jess Thompson, Keith Guttridge, April 25, 2016
- 7. Nearly 40% Of US Enterprises Will Adopt API Management Solutions By 2020 The US API management market will grow more than fourfold from $140 million in 2014 to $660 million by 2020. Forrester: Sizing The Market For API Management Solutions 2015
- 9. Scenario: A new mobile App
- 12. Price
- 13. Digital transformation Do it yourselfWebshop Devices IoTServices Mobile Cogniative Machine learning
- 16. United front
- 17. DEMO
- 18. Recap
- 19. Experience Layer System Layer Process Layer
- 21. Thanks! Mattias Lögdberg, Solutions Architect Email: Mattias. Logdberg@ibiz-solutions.se
Editor's Notes
- Investerat i BizTalk och hur för
- Digital transformering, Vad/Hur/Varför API’er, saas,paas, etc Molnet hört om deT? Det löser ju allt? Eller hur? Utvecklar idag, mobil/api first kosument eller publicerare
- Appar, telefon,padda,dator,tv,klocka Utan data TRÅKIG. Spotify/Netflix/Snapchat Förväntar oss data I alla devices Anlsutet, wifi/4g pada/telf/Dator etc ansluta allt överallt Ett eller flera sammankopplade api’er.
- Hybrid integration -> api’er Mobile vana vid “system” inte “appar/Devices” 70% mobil app -> api => 24/7 och SLA 99 Troligtvis api’er sakapas under projektet. Service Fönster/Skalbarhet/säkerhet/nya cred/cachning/överbelastning Dina/mina förväntningar
- Viktigt med stretegi, skenade kostnader. Vana vid system api’er, hantera ändringar/problem avstängning med okända brukare 24/7. Förväntar hög data kvalitet och tillgänlgighet Uppdaterings cykler Sverige längre fram EMPATI! Skrämande långt bort. ”Hur tacklar vi nya krav? Inte lätt, ”Särskilja” Utmaning, våra vanor förutsätter => nya krav (spotify) Förväntningar => ifrågasättande? (VPN) Normal/sund reaktion => bättre produkter/tjänster
- EDIFACT Slutet 1990 Korba (första inom SOA ) Java RMI och distributed COM SAO och SOAP <3 Nu flashight API löser det allt?
- A new project has started and it’s suppose to expose services inside the Company. As we saw earlier this is a common scenario. And from my experience something that is driven by buisness outside IT and often outside Integration supervision.
- Kanske DMZ? BizTalk exp massor av REST API och SOAP Olika objektsmodeller/säkerhet (arkitekturella mönster/projekt beslut) Virvarv av tekniker/objekt (vad är en order?) Vad händer IoT/mobil projektet? (anim) Hur förvaltas detta? Vad händer vid förändring? Hårda skapade beroenden.
- It grows Several diffrent systems, several diffrent endpoint urls (firewall openings) Diffrent data models, diffrent security Where to find errors? How to monitor? What about changes? 24/7 support etc 1 million users ? Impact in the source api’s, how to handle all these diffrent technologies and security solutions
- Markets are under price press Compensate by sell more quantity (good creates work and volume) Efficiency matters, Production has been focused
- Webshops been added, in building supplies ”do it yourself” Services as ”inventory management”
- Customers want information, help, comparements information. Why your drills? (we provide 30% longer effective run time, and we notify when it’s about to run out with an order confirmation for a new one, so you will have it in time for the change) By giving this type of services we now can sell on more than just price
- Första delen objektsmodell Löjligt, men hur tänker ni?(jämför SAOP,REST,Flatfile,SAP)? Säkerhetsmodeeller, (pass,user,certificat) Begräsningar? 1-100 anv. -> 1 miljon? Cache,
- Objects modell (förstår vad som skickas) Säkerhet på samma sätt Efter implementerat en tjänst alla till alla. Snyggt och prydligt. Återanvändning!
- Explain the demo Logic App cloud integration flow, protected by SAS token and has really bad URL’s Rest Service, Exposed and protected by API Key, speciall message’s need to be sent. XML Service a OPEN SOAP api, no protection
- Recap! Enkelt att sprida och förvalta! Ser lika ut, samma modeller, authentisering. In a big enterprise this is very important to create the possiblitites that are needed to creart
- Ta ägarskap, Återkoppla till Historien, RBAC,SOA. GÖR inte samma fel igen. Återkoppla vanlig setup, se till att ni tar ägarskap, låt inte Projektet/PoC’n styra! Återkoippla löven, visa at vår kund, gjorde det och så kan ni!