Enabling digital transformation api ecosystems and data virtualization
•
4 recomendaciones•614 vistas
Watch the full webinar here: https://buff.ly/2KBKzLJ Digital transformation, as cliché as it sounds, is on top of every decision maker’s strategic initiative list. And at the heart of any digital transformation, no matter the industry or the size of the company, there is an application programming interface (API) strategy. While API platforms enable companies to manage large numbers of APIs working in tandem, monitor their usage, and establish security between them, they are not optimized for data integration, so they cannot easily or quickly integrate large volumes of data between different systems. Data virtualization, however, can greatly enhance the capabilities of an API platform, increasing the benefits of an API-based architecture. With data virtualization as part of an API strategy, companies can streamline digital transformations of any size and scope. Join us for this webinar to see these technologies in action in a demo and to get the answers to the following questions: *How can data virtualization enhance the deployment and exposure of APIs? *How does data virtualization work as a service container, as a source for microservices and as an API gateway? *How can data virtualization create managed data services ecosystems in a thriving API economy? *How are GetSmarter and others are leveraging data virtualization to facilitate API-based initiatives?
Recomendados
Recomendados
Más contenido relacionado
La actualidad más candente
La actualidad más candente (20)
Similar a Enabling digital transformation api ecosystems and data virtualization
Similar a Enabling digital transformation api ecosystems and data virtualization (20)
Más de Denodo
Más de Denodo (20)
Último
Último (20)
Enabling digital transformation api ecosystems and data virtualization
- 1. Enabling Digital Transformation: API Ecosystems and Data Virtualization (EMEA) Paul Moxon SVP Data Architectures & Chief Evangelist August 2019
- 2. Paul Moxon SVP Data Architectures & Chief Evangelist, Denodo Speakers
- 3. 1. Digital Transformation and the API Economy 2. Current Trends with APIs 3. Data Virtualization in the API Ecosystem 4. Demo 5. Q&A 6. Next Steps Agenda
- 4. Digital Transformation and the API Economy 4
- 5. 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. 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
- 7. 7 Example from the API Economy – Uber Google Maps MapKit (iOS) Twilio SendGrid • APIs have allowed Uber to focus on its core business • Connecting drivers with riders • Critical services are provided by technology partners via APIs • Braintree for payments, Google Maps for driver tracking, etc. • Uber has also exposed APIs to partners • Uber has become a platform
- 8. 8 The Value of Platforms Driven by APIs • Five most valuable* companies in 2018 were platform providers: Apple $890B Google $768B Microsoft $680B Amazon $592B Facebook $545B * Valuation based on market capitalization Exxon $492B General Electric $358B Microsoft $313B AT&T $238B Proctor & Gamble $236B Source: Bloomberg, Google Compare to 2008 top 5:
- 9. 9 • Google have exposed Maps functionality through APIs • Many companies use these APIs to show locations • e.g. Uber, Fedex for tracking • e.g. retailers – e.g. Starbucks – for store locations • e.g. companies – such as Denodo – for office locations API Example – Google Maps
- 10. Current Trends with APIs
- 11. 11 API Protocols • The 90’s: CORBA ‒ Common Object Request Broker Architecture ‒ Available since 1991 ‒ Programming specification for distributed applications in heterogeneous environments ‒ Relatively abstract and complex model; difficult to implement • The 2000’s: SOAP ‒ Simple Object Access Protocol ‒ Available since 1999 ‒ Industrial standard of the World Wide Web Consortiums (W3C) ‒ Application protocol: SOAP over HTTP ‒ Payload: Services Definition Language (WSDL) authored in XML ‒ Complex and heavyweight/verbose protocol, slow parsing • The 2010’s: REST ‒ Became the de facto standard for web services
- 12. 12 RESTful API The de facto standard for web services • Not a detailed specification, but a programming paradigm ‒ 6 architectural constraints: Client/Server, stateless, uniform interface, cacheable, layered system, code on demand • HTTP as the application protocol ‒ The HTTP methods (GET, POST, PUT, ...) indicate which operation a service should perform ‒ Light-weight payloads in HTML, JSON or XML ‒ Services are addressed via URL ‒ Examples from Salesforce ▪ https://salesforce.../Query/?q=SELECT+Name+From+Account+WHERE+ShippingCity='San+Francisco' ▪ https://salesforce.../Account/001D000000INjVe?fields=AccountNumber,BillingPostalCode • Many other protocols have been created to facilitate this approach ‒ Consumption Protocol: OData, GData ‒ Authentication: OAuth, SAML ‒ Interface specifications: WADL, OpenAPI (i.e. Swagger)
- 13. 13 Microservices Evolving software-driven, cloud-native service delivery infrastructures • 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 • They are typically exposed as RESTful Web Services
- 14. 14 API Management and Microservices • Gateway: network routing, throttling and security • Publishing: deploy APIs, versioning and coordinate the overall API lifecycle • Portal: community site for API users, information and functionality including documentation • Reporting and analytics: functionality to monitor API usage and load • Monetization: metering and chargeback based on usage Gartner: “Full life cycle application programming interface (API) management is about the planning, design, implementation, testing, publication, operation, consumption, maintenance, versioning and retirement of APIs.” Example: Azure API Management
- 15. Data Virtualization in the API Ecosystem
- 16. 16 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 integration layer for Microservices 3. Data Virtualization as a Data Services Layer for Microservices
- 17. 17 ? Denodo as a Data Service Provider API GATEWAY DATA CONSUMERSDATA CONSUMERS MICROSERVICES DISPARATE DATA SOURCES
- 18. 18 Denodo as a Data Service Provider • CONNECT: connect disparate data from any source (enterprise, Big Data, cloud, Excel) or location • COMBINE: define data transformations and combinations that meet your business needs • PUBLISH: one-click REST web services deployment, establishing the REST practices ‒ Protocol: Denodo’s REST format, OData 2.0 and OData 4.0 ‒ Payload: XML, JSON, RSS and HTML ‒ Authentication: Basic HTTP, SPNEGO (Kerberos), OAuth, SAML ‒ Documentation: OpenAPI (i.e. Swagger)
- 19. 19 Denodo as an Integration Layer for Microservices API GATEWAY DATA CONSUMERSDATA CONSUMERS MICROSERVICESDISPARATE DATA SOURCES
- 20. 20 Denodo as Integration Layer for Microservices • Keep the Microservice lightweight ‒ Leverage Denodo’s data management services ▪ caching, security, auditing, data cleansing, resource management, … • Combine Data ‒ Transform and combine data from different sources • Better Usability ‒ Single point of entry ‒ Same protocol ‒ Global Data Catalog
- 21. 21 Fundamental Data APIs (Read-only) Business Logic APIs Business Process APIs Data Aggregation APIs Denodo as a Data Services Layer for Microservices Price Promo Customer Location Tax Order Item Worker Vendor MICROSERVICES
- 22. 22 Business Process APIsBusiness Process MicroservicesBusiness Logic APIsBusiness Logic Microservices MICROSERVICES Fundamental Data APIs (Read-only) Data Aggregation APIs Denodo as a Data Services Layer for Microservices Price Promo Customer Location Tax Order Item Worker Vendor Fundamental Data APIs (Read-only) Data Aggregation APIs
- 23. 24 Denodo as a Data Services Layer for Microservices • Keep the Microservice lightweight ‒ Avoid programming data access patterns into microservice logic (e.g. SQL queries) • Keep the Microservice database independent ‒ No direct access to databases – data accessed from Data Services Layer ‒ Easier deployment & migration ‒ True Microservice scalability • Leverage advanced optimizations of Denodo Platform ‒ Avoid having to tune queries in Microservices layer
- 24. 25 Business Process MicroservicesBusiness Logic Microservices MICROSERVICES Fundamental Data APIs (Read-only) Data Aggregation APIs Denodo as a Data Services Layer for Microservices – CQRS Price Promo Customer Location Tax Order Item Worker Vendor Fundamental Data APIs (Read-only) Data Aggregation APIs Write APIs CQRS = Command-Query Responsibility Separation
- 26. 27 Case Study – Leading Fast Food Restaurant • Leading ‘fast food’ restaurant chain in North America • Over 2,300 locations • Built smart phone app – used by millions of customers • Order food for pick up, find locations, review nutrition information, etc. • Menu (main, sides, drinks) can vary by location • Menu details and food nutrition information retrieved by app based on user location • Data retrieved via REST APIs served by Denodo Platform • Menu data in databases, files, Excel spreadsheets • Read by Denodo Platform, exposed to app via REST APIs
- 27. 28 Case Study – Leading Fast Food Restaurant
- 28. 29 Case Study – GetSmarter, Leader in Online Education • GetSmarter has implemented a microservice architecture that works in tandem with the Denodo platform to simplify data access throughout its organization. • With Denodo Platform, GetSmarter provides data to stakeholders, from any type of system, microservice or historical system, in real time, without affecting business flows. • Not only does the new architecture provide a single view of core business entities, but it also allows GetSmarter to migrate data from legacy systems in the background, without users noticing the change. More info: http://www.datavirtualizationblog.com/getsmarter-accelerated-business-decisions-single-view-across-rapidly-evolving-infrastructure/
- 29. Demo 30
- 31. Key Takeaways
- 32. 33 Use Data Virtualization to simplify and accelerate your API initiatives… • Connect to all your data • Central point for data transformation, combination, security and governance • One-click REST Web Services deployment API-tize Your Data
- 33. Q&A
- 34. 35 Next Steps Access Denodo Platform in the Cloud! Take a Test Drive today! www.denodo.com/TestDrive GET STARTED TODAY
- 35. Thanks! www.denodo.com info@denodo.com © 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.