L’API Economy ha permesso ad aziende e startup di fornire i propri servizi attraverso nuovi canali. La nascita di ecosistemi digitali interaziendali ha spinto ulteriormente molte aziende ad inserire nel loro piano di Digital Transformation programmi di sviluppo ed esposizione di API interne ed esterne per aumentare l'integrazione aziendale e abilitare nuovi modelli di business con terze parti. Ma esporre delle API non è sufficiente. Nell'API Economy diventa fondamentale sviluppare una strategia di commercializzazione delle API e un'architettura in grado di abilitare transazioni commerciali.

1. La monetizzazione delle API
Francesco Arcieri
CODEMOTION MILAN - SPECIAL EDITION
11 NOVEMBER 2017

2. 2
API Economy
Le API sono alla base della Digital Trasformation e la loro crescita è esponenziale.
Projected Open API Growth Rate. Source: Craig Burton and Phil Windley
Entro il 2020 il 60% del mercato IT
sarà generato tramite APIs
IBM Institute for Business Value

3. 3
Ciclo di vita della Commercializzazione di un’API
Back-end
APIs
Mediated API
(ex: REST-to-SOAP, XML-to-
JSON, HTTP-to-JMS, …)
Security Enforced API (opz)
(Throttling, schema validation, content filtering, …)
Mash-up API
(internal+internal, internal+external, … )
Virtualized
API
Service Plan Creation
(Pay per Use, Flat, …)
API
Gateway
Exposed API
Published API
(Technical documentation, …)
Monetized API
Possibilità di agganciare diversi sistemi back-end, sia interni che di
terze parti.
La piattaforma permette di eseguire diverse operazioni sulle API di
back-end, più o meno complesse, a seconda dal risultato desiderato
(es. virtualizzazione o mash-up).
L’API è tecnicamente fruibile, ma è priva delle logiche di
commercializzazione. In questa fase la API va arricchita con la relativa
documentazione tecnica.
Se necessario, si arricchiscono le API con delle policies specifiche
(security, throttling, etc).
Le capabilities delle API di back-end vengono ‘esposte’ sull’API
Gateway.
L’integration Layer è responsabile della sincronizzazione del catalogo
API, del provisioning e del metering delle API.
Per le differenti API vengono creati i piani di servizio che ne
permetteranno la monetizzazione tramite i modelli di business definiti
(consumo, flat, etc).
Le API vengono arricchite della descrizione commerciale e
monetizzate su un marketplace.
Integration Layer
Billing
Platform
API
STORE

4. 4
TIM OPEN API Management: Reference Architecture
External
Capabilities
Microservices
Layer
(Rest Interfaces)
Back-end
Capabilities
3°
parties
APIs
API Domain
Back-End
API GATEWAY
Web
Services
Data
Sources
SW
acquired
SW
developed
SW already
availableSystems
Legenda
API
API Domain
RESTAPI
Other
Platform/s

5. 5
TIM OPEN API Management: Reference Architecture
External
Capabilities
Microservices
Layer
(Rest Interfaces)
API Product
Manager
Create &
Publish API
Front-end API GATEWAY
Rate Limit AuthenticationTransformation Logging Metering
API
Monitoring
Back-end
Capabilities
3°
parties
APIs
API Domain
Back-End
API GATEWAY
Caching
Web
Services
Data
Sources
API
MANAGEMENT
Monitoring
& Control
SW
acquired
SW
developed
SW already
availableSystems
Legenda
API
API
Manager
API Domain
RESTAPI
Other
Platform/s

6. 6
TIM OPEN API Management: Reference Architecture
External
Capabilities
Subscribe API
FRONT-END
Manage API and APPs
Microservices
Layer
(Rest Interfaces)
API Store
Developer
API Product
Manager
Create &
Publish API
Identity
Management
Front-end API GATEWAY
Rate Limit AuthenticationTransformation Logging Metering
API
Monitoring
Back-end
Capabilities
3°
parties
APIs
ENTERPRISE
SYSTEMS
API Domain
Back-End
API GATEWAY
Caching
API Portal
BSS & OSS systems
Integration Layer
Web
Services
Data
Sources
API
MANAGEMENT
Monitoring
& Control
SW
acquired
SW
developed
SW already
availableSystems
Legenda
API
API
Manager Provisioning Catalogue Metering
API Domain
RESTAPI
Other
Platform/s

7. 7
TIM OPEN API Management: Reference Architecture
External
Capabilities
Subscribe API
FRONT-END
Manage API and APPs
Microservices
Layer
(Rest Interfaces)
API Store
Developer
Develop APP
API Product
Manager
Create &
Publish API
Identity
Management
Front-end API GATEWAY
Rate Limit AuthenticationTransformation Logging Metering
API
Monitoring
Use API
Back-end
Capabilities
3°
parties
APIs
ENTERPRISE
SYSTEMS
API Domain
Back-End
API GATEWAY
APP
Caching
API Portal
BSS & OSS systems
Integration Layer
Web
Services
Data
Sources
API
MANAGEMENT
Monitoring
& Control
SW
acquired
SW
developed
SW already
availableSystems
Legenda
API
API
Manager Provisioning Catalogue Metering
API Domain
RESTAPI
Other
Platform/s
End User
Use APP

8. 8
TIM OPEN API Management: Reference Architecture
External
Capabilities
Subscribe API
FRONT-END
Manage API and APPs
Microservices
Layer
(Rest Interfaces)
API Store
Developer
Develop APP
API Product
Manager
Create &
Publish API
Identity
Management
Front-end API GATEWAY
Rate Limit AuthenticationTransformation Logging Metering
API
Monitoring
Use API
Back-end
Capabilities
3°
parties
APIs
ENTERPRISE
SYSTEMS
API Domain
Back-End
API GATEWAY
APP
Caching
API Portal
BSS & OSS systems
Integration Layer
Web
Services
Data
Sources
API
MANAGEMENT
Monitoring
& Control
SW
acquired
SW
developed
SW already
availableSystems
Legenda
API
API
Manager
End User
Use APP
Provisioning Catalogue Metering
Consumption
Repository
Consumption
DB
DB write API
API Domain
RESTAPI
Other
Platform/s

9. 9
ENTERPRISE
SYSTEMS
TIM OPEN API Management: Reference Architecture
TIM API
MANAGEMENT
LAYER
API GATEWAY
Rate Limit Authent.Transf. Caching LoggingMeter
Connector
Provisioning
API (3)
Catalogue
API (2)
Metering
API (4)
(2): API that exposes all the
available APIs on API GW
(3): On new order a provisioning
request ask to authorize User X for
API Y with Rate Limit Z
(4): API that exposes
all consumption
information of API Y
New API/Unpublished
Notification (1)
(1): API GW will send a
trigger to this API to
notify that new APIs
are available on Axway
BSS & OSS systems
SW
acquired
SW
developed
SW already
available
Legenda

10. 10
ENTERPRISE
SYSTEMS
BSS & OSS systems
Metering by Calls
SW
acquired
SW
developed
SW already
available
Legenda
API GATEWAY
API Domain
Microservice
metered by Call
(es: SMS)
Meter
Connector
Metering APIs
Native Metering DB
Consumptions API (ByDev, ByAPI)
Calls
Calls
TIM API – InviaSMS
Calls
API
MANAGEMENT
Connector calls Consumption API
every configurable period (es: 1H)
Connector calls Consumption API in real
time for Subscription cancellation

11. 11
ENTERPRISE
SYSTEMS
BSS & OSS systems
Metering by Credits
SW
acquired
SW
developed
SW already
available
Legenda
API GATEWAY
API Domain
Microservice
metered by Call
(es: SMS)
Meter
CONSUMPTION
REPOSITORY
Connector
Metering APIs
Native Metering DB
Consumptions API (ByDev, ByAPI)
Calls
Credits
CallsCredits
Consumption DB
API Domain
Microservice
metered by Credits
(es: Atoka)
Atoka-AroundMe TIM API – InviaSMS
Calls
API
MANAGEMENT

12. 12
ENTERPRISE
SYSTEMS
BSS & OSS systems
Metering by other measures
SW
acquired
SW
developed
SW already
available
Legenda
API GATEWAY
API Domain
Microservice
metered by Call
(es: SMS)
Meter
CONSUMPTION
REPOSITORY
Consumption DB
Write API
Connector
API Domain
Microservice
metered by
other units
Metering APIs
Native Metering DB
Consumptions API (ByDev, ByAPI)
GB
Calls
Credits
Calls
Other units
of measure
Consumption DB
API Domain
Microservice
metered by Credits
(es: Atoka)
Atoka-AroundMe
TIM API –
Object Storage
TIM API – InviaSMS
Calls
API
MANAGEMENT

13. 13
TIM OPEN: API STORE

14. 14
Francesco Arcieri
Francesco.Arcieri@Olivetti.com
https://www.linkedin.com/in/francescoarcieri/