Cloud Elements | State of API Integration Report 2018
0 likes177 views
The 2018 State of API Integration report outlines key findings from a survey on API integration trends and predicts future industry changes. It highlights the shift from selling products to platforms, the disruptive nature of low-code/no-code solutions, and the importance of security in API lifecycle management. Additionally, it discusses various emerging API styles such as OData, REST, and GraphQL, emphasizing their capabilities and relevance in integration scenarios.
Cloud Elements | State of API Integration Report 2018
- 2. THE STATE OF API INTEGRATION REPORT 2018 This report covers key findings from the survey we distributed to collect insights into the state of API Integration. It will share our predictions on how these findings will change the industry in 2018 and beyond. We will explore prominent themes, including the expectation that APIs ease integrations, rather than stifle it, and that successful applications should be more like platforms than products.
- 7. PLATFORM VS PRODUCT Today’s most successful software companies have made the leap from selling products to selling a platform. The appeal of such a move is understandable: software products generate only a single revenue stream, while platforms, by connecting different groups of users and services, can generate multiple revenue streams.
- 10. LOW CODE/NO CODE The burgeoning Low-Code/No-Code space has become an extraordinarily disruptive force in the domain of API integration - causing confusion amongst developers, users and even vendors. But even the terminology itself can be misleading, as the distinction isn’t about whether people need to code or not - but rather about the types of people using technology and tools to build API integration.
- 19. SERVER-SENT EVENTS Although the term Server-Sent Events(SSEs) may be unfamiliar, the idea behind SSEs should be familiar: allowing a Web Application to “subscribe” to data updates originated (sent) by a server, and subsequently be notified as these data events occur. The problem with SSEs is that, while they remove the polling technically, they also take much of the control from the user and forces the user into a passive state.
- 20. WEB SOCKETS WebSockets provide a richer protocol to perform bidirectional, full duplex communication. This two-way channel is more attractive for things like games, messaging apps, interactive experiences, and for cases where you need real-time updates in both directions. But again, the solution isn’t perfect as the integration pattern effectively breaks the semantics of HTTP.
- 21. WEBHOOKS
- 23. “Security teams must deliver ‘security as code’, that is, translate security requirements into code that can run automatically at every step of the API lifecycle.”Isabelle Mauny Co-founder & CTO, 42Crunch - @isamauny
- 24. SECURITY CANNOT BE A LAST MINUTE ADDITION NOT JUST KEEPING THE BAD GUY OUT DEVELOPER EXPERIENCE
- 27. ODATA Originally developed by Microsoft in 2007, OData is an OASIS standard REST API well established among companies such as Microsoft, SAP, IBM and Salesforce. - Allows the creation and consumption of queryable and interoperable RESTful APIs in a simple and standard way - Gives you a rich set of querying capabilities - Open source approach and exceptional scalability
- 28. REST API REST (representational state transfer) or RESTful web services are one way of providing interoperability between computer systems on the internet. - REST-compliant web services allow requesting systems to access and manipulate textual representations of web resources using a uniform and predefined set of stateless operations - RESTful implementations make use of standards such as HTTP, URI, JSON and XML - REST is an architectural style, not a standard
- 29. GRAPH QL Developed internally at Facebook in 2012, before public release in 2015, GraphQL is a data query language deployed at companies such as Facebook, Shopify and Intuit. - Provides a complete and understandable description of the data in your API - Gives clients the power to ask for exactly what they need - Makes it easier to evolve APIs over time and enables powerful developer tools.
- 30. In order to compile the most comprehensive breakdown of the industry’s trends and highlights, we need your insights! Contribute to the State of API Integration 2019 Report by taking this survey. #StateofAPIIntegration
- 31. READ MORE Full State of API Integration Report 2018 State of API Integration Infographic #StateofAPIIntegration