The Role of Data Virtualization in an API Economy
1 like284 views
The document discusses a webinar series focused on data virtualization and its role in the API economy during digital transformation. It highlights the importance of APIs as foundational elements for integrating IT systems, driving digital initiatives, and outlines trends in API development and microservices architecture. Additionally, it showcases how Denodo's data virtualization can facilitate API management and data services, illustrated with a customer case study by GetSmarter.
The Role of Data Virtualization in an API Economy
- 1. DATA VIRTUALIZATION PACKED LUNCH WEBINAR SERIES Sessions Covering Key Data Integration Challenges Solved with Data Virtualization
- 2. The Role of Data Virtualization in an API Economy Pablo Alvarez-Yanez Director of Product Management, Denodo
- 3. Agenda 1. An Introduction: APIs in the Age of Digital Transformation 2. Current API trends 3. Data Virtualization in the API ecosystem 4. Customer Story 5. Demo
- 4. APIs and in the age of Digital Transformation 4
- 5. Digital Transformation • Digital transformation is a strategic initiative for most organizations • The concept reflects technology’s role in strategic decision-making, with its ability to automate and simplify business processes, improve customer relationships, enhance productivity, and cost savings • Driven from CEO’s office: Highest level of visibility & fully funded • Gartner – 28% of CIO budget in 2018 • IDC – 2/3 of CEOs in global 2000 have digital transformation in the center of their corporate strategy • Seen as do-or-die initiative • “If you don’t, someone else will”
- 6. APIs – Building Blocks of Digital Transformation • API stands for Application Programming Interface • APIs are the foundations of digital transformation • Enable the integration of diverse IT systems, building more collaborative and self-service IT environments • Exposing data and processes as APIs allows creation of new products and business models • Create revenues from existing IT assets • These initiatives have created an API economy
- 8. Protocols, Protocols Efforts to standardize communications between applications are not new • CORBA in the 90’s • SOA architectures and SOAP web services in the early 2000’s The explosion of cloud-first initiatives and SaaS applications made REST services the de facto standard of the 2010’s • HTTP as the application protocol • HTTP verbs (GET, POST, PUT, DELETE) to indicate the action on the resource • Light-weight payloads in JSON or XML But REST is not a standard, but an architectural approach. Many other protocols have been created to standardized different parts of this approach • Consumption Protocol: OData, GData • Security: OAuth, SAML • Specifications: WADL, OpenAPI (p.k.a. Swagger) 8
- 10. Down the Rabbit Hole… • Microservices philosophy: • Applications should be built from small, modular, lightweight, and independently deployable components (called microservices) • Microservices are reusable and easily scalable • Microservices are independently replaceable and upgradeable • Microservices can use different languages and technologies • The are typically exposed as RESTful Web Services
- 11. Microservices and API Management To keep microservices lightweight and easily scalable: • Move security and management out of the service container API Management Layer • Security policies • Access Controls • Routing Policies • Service Monitoring • Service Throttling • Caching
- 12. Functionality of API Management Tools 1. Automate and control connections between an API and the applications that use it. 2. Ensure consistency between multiple API implementations and versions. 3. Monitor traffic from individual apps. 4. Provide memory management and caching mechanisms to improve application performance. 5. Protect the API from misuse by wrapping it in security procedures and policies.
- 13. Data Virtualization in the API ecosystem 13
- 14. Data Virtualization in the API Ecosystem Data virtualization platforms like Denodo can play a significant role in an API ecosystem. Let’s review three common architectures: 1. Data Virtualization as a Data Service provider 2. Data Virtualization as an abstraction data layer form Microservices 3. Data Virtualization as an API Management tool 14
- 15. 15 1. Denodo as a Data Service provider API Gateway Other Enterprise Applications Microservices
- 16. 1. Denodo as a Data Service provider Denodo provides one-click, zero development REST web services on top of any data model Flexible web services with full-fledge capabilities: • Support XML, JSON, RSS and HTML • Support for hierarchical structures • Authentication with basic HTTP, SPNEGO (Kerberos), OAuth 2.0 and SAML • Self documented with OpenAPI (pka Swagger) • Available in Denodo’s REST format, OData 2.0 and OData 4.0 • Navigation to related resources via links and $expand operator • IDU support with different HTTP verbs (GET, POST, PUT, DELETE) • Support for READ via POST to handle large input parameters • Support for CORS and JSONP
- 17. 17 2. Denodo as abstraction data layer form Microservices API Gateway Other Enterprise Applications Microservices
- 18. 2. Denodo as a Data Service provider Denodo can serve as an abstraction between the microservice implementation and the data access to simplify its development • It enables technology changes in the backend without affecting the code of the Microservice (e.g. legacy system migrations, vendor switch, etc.) Microservices principles avoid performing data integration at the Microservice itself • Using DV as a backend enables the independence of the Microservice from the integration techniques • The integration logic is performed in the DV layer in the form of virtual views Although potentially each Microservice could have its own DV backend, a logical separation per microservice (a schema) is usually a more realistic architecture
- 19. 19 3. Denodo as an API Management Tool Other Enterprise Applications Microservices
- 20. 3. Denodo as an API Management Tool Since external APIs and web services can be registered in Denodo as data sources, Denodo’s capabilities can act as a sort of API gateway: • Centralized authentication and authorization • Monitoring and access auditing • Resource allocation policies (e.g. max 10 queries per hour for userA to service) • Unified catalog • API integration However, keep in mind that is not an API gateway per se, and it may significantly change the structure and capabilities of your external APIs when exposed through the virtual layer
- 22. 22 Get Smarter – Online Education 22 GetSmarter implemented a microservices architecture working in tandem with the Denodo Platform, to streamline data access across the organization. With the Denodo Platform in place, GetSmarter could provide data to stakeholders from any microservice or legacy system, in real time, without causing any disruption in the business flow. Not only did the new architecture provide the single view of core entities, it also enabled GetSmarter to migrate data from legacy systems behind the scenes, without users being aware of the change. More info: http://www.datavirtualizationblog.com/getsmarter-accelerated-business-decisions-single-view-across-rapidly-evolving-infrastructure/
- 23. Demo 23
- 24. Q&A
- 25. Next steps Take Denodo for a Test Drive on the Cloud Explore the benefits of data virtualization for Agile BI and Analytics
- 26. Next session Innovative Data Strategies for Advanced Analytics Solutions and the Role of Data Virtualization Thursday, October 18, 2018 | 11:00 AM PT / 2:00 PM ET Lorrin Ferdinand Sr. Consultant, Neudesic
- 27. Thank you! © Copyright Denodo Technologies. All rights reserved Unless otherwise specified, no part of this PDF file may be reproduced or utilized in any for or by any means, electronic or mechanical, including photocopying and microfilm, without prior the written authorization from Denodo Technologies.