Watch full webinar here: https://buff.ly/2KTz2IB
Most people associate data virtualization with BI and analytics. However, one of the core ideas behind data virtualization is the decoupling of the consumption method from the data model. Why should the need for data requests in JSON over HTTP require extra development? Denodo provides immediate access to its datasets via REST, OData 4, GeoJSON and other protocols, with no coding involved. Easy to scale, cloud friendly and ready to integrate with API management tools, Denodo can be the perfect tool to fulfill your API strategy!
Attend this session to learn:
- What’s the role of Denodo in an API strategy
- Integration between Denodo and other elements of the API stack, like API management tools
- How easy it is to access Denodo as a RESTful endpoint
- Advanced options of Denodo web services: OAuth, OpenAPI, geographical capabilities, etc.
4. 4
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
Enables exposing data and processes to other business
units and/or partners
Create revenues from existing assets, and support
creation of new products and business models
These initiatives have created an API Economy
5. 5
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
6. 6
API Management Lifecycle: API Gateways
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
7. 7
Data Virtualization in the API Ecosystem
Denodo Vision: expose data to any consumer from
any source and in the desired format
Data virtualization platforms like Denodo can play
a significant role in an API ecosystem
Let’s review some 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
8. 8
Denodo as a Data Service Provider
API Gateway
Other Enterprise
Applications
Transactional Services
9. 9
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, with
zero code
PUBLISH: one-click REST and SOAP web services deployment
Protocol: Denodo’s REST format, OData 2.0, OData 4.0, GraphQL
Payload: XML, JSON, RSS and HTML
Documentation: OpenAPI (i.e. Swagger)
Linked Data Services generated from Associations in Denodo Model
14. 14
Denodo as a Data Service Provider (and 2)
SECURITY: leverage full Denodo security model (roles, cell-level security,…)
Authentication: Basic HTTP, SPNEGO (Kerberos), OAuth, SAML
CORS Support
PERFORMANCE: automatic query optimization
Best query optimizer in the market for distributed query execution
Multiple caching strategies
MANAGEMENT: quotas, workload management, monitoring,…
15. 15
GraphQL provides a query language for APIs:
GraphQL is normally used as an abstraction layer between UI and REST
services
Decreases number of API requests
Removes orchestration from the UI when obtaining data
Denodo can provide declarative execution of GraphQL queries on top of
Denodo’s virtual data model, with zero code:
Security, Optimization, Lineage…
Enables graph-like queries on top of any data source
GraphQL Access to Denodo
17. 17
0
100
200
300
400
500
600
700
800
900
1000
2013 2014 2015 2016 2017
Growth of Data Services
Goal Actual Projected
Central Tenets
• Focused on reuse
• Time to market is a key value proposition
• Security and governance is designed in and enforced
Growth of DV at Intel
• 1000+ internal users trained on DV tools and
capability
• 23/26 logical business areas now using data
virtualization.
• > 1000 data services production from 309 data
sources.
• All IT targets for business adoption have been
exceeded.
• All BU’s recognizing 50-80% productivity gains
DV at Major Semi-Conductors Vendor
18. 18
Microservices
Typically used in the context of operational applications
Microservices philosophy
Applications should be built from small, modular, lightweight, and
independently deployable components
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
Not for every use case: can significantly increment complexity
19. 19
Microservices and Denodo
Denodo can be easily containerized for data
microservices
Denodo can simplify microservices architectures in
several ways:
Combine different microservices in layered
microservices architectures (core, composite,
gateway,…)
Simplify data access in microservices, while
maintaining microservice change isolation
20. 20
Denodo as an Integration Layer for Microservices
API GATEWAY
DATA CONSUMERSDATA CONSUMERS
MICROSERVICESDISPARATE DATA SOURCES
21. 21
Denodo as Integration Layer for Microservices
Simplify Composite and BFF Microservices
Leverage Denodo’s data management
services
Caching, security, auditing, data cleansing,
resource management, …
Combine Data
Transform and combine data from different
sources
22. 22
Denodo as a Data Services Layer for Microservices
Price Promo Customer Location Tax Order Item Worker Vendor
MICROSERVICES
23. 23
Microservice Pattern: Each Microservice has its own Database
Purpose: maximize Microservice independence
Changes in data schema do not affect other
microservices
Each microservice can use its own type of database
Problem: difficult to implement and manage
Splitting databases is hard, often impossible
Problem: combining data for joins and reporting:
Some architectures replicate data in a different
repository using event-based data capture
MICROSERVICES
24. 24
Denodo as a Data Services Layer for Microservices
MICROSERVICES
Fundamental Data APIs (Read-only)
Price Promo Customer Location Tax Order Item Worker Vendor
Fundamental Data APIs (Read-only)
Data Reporting
25. 25
Denodo as a Data Services Layer for Microservices
DV is the API for accessing data from other
microservices
Schema can be changed without affecting other
microservices, even in a shared database
Consumers can be isolated of transition (if done)
No need for an additional repository for joins and
reporting
Leverage advanced optimizations of Denodo
Platform
Use caching if needed
Pushdown functionalities
MICROSERVICES
Fundamental Data APIs (Read-only)
Price Promo Customer Location Tax Order Item Worker Vendor
Fundamental Data APIs (Read-only)
Data Reporting
26. 26
GetSmarter, Leader in Online Education
• GetSmarter has implemented a
microservice architecture in tandem with
the Denodo platform to simplify data
access throughout its organization.
• With Denodo, GetSmarter provides data
to stakeholders, from any type of system,
microservice or historical system
• 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/
28. 28
Creation of API
Connect to data
sources and create
base views
Apply transformations
to the data into a if
needed
Identify Data that
needs to be made
available in the form
of an API
Create APIs and consume
them through applications,
microservices or other API
management platforms
29. 29
What’s the impact on total sales
of a new marketing campaign for
each country?
Historical sales data offloaded to
Hadoop cluster for cheaper storage
Marketing campaigns managed in an
external cloud app
Country is part of the customer
details table, stored in the DW
Sources
Combine,
Transform
&
Integrate
Consume
Base View
Source
Abstraction
join
group by
country
join
Sales Campaign Customer
Demo Scenario
32. 32
Key Takeaways
Denodo and data virtualization can play a crucial role in Data Services and API
Management Architectures
Denodo allows generating data services from any data source in minutes, using multiple
protocols and supporting all major security and documentation standards
Denodo can greatly simplify data access and combination in Microservices architectures
33.
34. 34
Next Steps
Access Denodo Platform in the Cloud!
Take a Test Drive today!
www.denodo.com/TestDrive
G E T S TA R T E D TO DAY