Scaletta del talk: Introduzione: Chi è Profesia/WSO2 Cosa è un Identity server Ruolo di Identity server in architettura Panoramica feature Identity server Configurazione social Google Login con google e non con un esempio Considerazioni finali

3. Vai al gruppo

4. API Management

5. APIM Architecture

6. Distributed consumer API
Gateway Environment
<Environments>
<Environment type="hybrid" api-console="true" isDefault="true">
<Name>WEST</Name>
<Description>WEST</Description>
<ServerURL>https://192.168.116.180:${mgt.transport.https.port}/services/</ServerURL>
<Username>${admin.username}</Username>
<Password>${admin.password}</Password>
<GatewayEndpoint>https://westserver:${https.nio.port},http://westserver:${http.nio.port}</GatewayEndpoint>
<GatewayWSEndpoint>ws://westserver:9099,wss://westserver:8099</GatewayWSEndpoint>
</Environment>
<Environment type="hybrid" api-console="true" isDefault="true">
<Name>EST</Name>
<Description>EST</Description>
<ServerURL>https://estserver:${mgt.transport.https.port}/services/</ServerURL>
<Username>${admin.username}</Username>
<Password>${admin.password}</Password>
<GatewayEndpoint>https://estserver:${https.nio.port},http://estserver:${http.nio.port}</GatewayEndpoint>
<GatewayWSEndpoint>ws://estserver:9099,wss://estserver:8099</GatewayWSEndpoint>
</Environment>
</Environments>

7. Distributed Services

8. micro Gateway
API decentralization

9. MicroGateway

10. How the API Microgateway works

11. MicroGateway main Feature
Its main characteristics are:
● The ability to execute in isolation without mandatory connections to other
components (Key Manager, Traffic Manager, etc).
● The ability to host only a subset of specific APIs (defined in the API
Publisher), instead of all.
● Immutability; if you update an API, you need to re-create the
container/instance and hot deployment is not possible.
Microgateway offers you a proxy that is capable of performing security validations
(OAuth, Signed JWT), in-memory (local) rate limiting and operational analytics.

12. API Microgateway developer workflow

13. Design and deployment comparison
Design/ Deployment API Microgateway API Gateway
Architecture Designed for microservices Designed for monolith
Horizontal Scaling Scales independently Scaling can be done with other components
Deployment Distribution Decentralized Centralized
Runtime footprint Lightweight (2vcpu 256MbRam) Designed to run on high performing
computers with high load
Isolated lockdown
environments
Designed to work in a network isolated environment Limited functionalities(affect on throttling/
analytics)
Cloud Ready Yes Yes
Automated API CI/CD flows Supported with CLI tools Supported with CLI tools
Update APIs Immutable gateways. Rebuild the gateway upon
updating the API
Mutable gateway, updating APIs supported

14. Security Comparison
Security Mechanism API Microgateway API Gateway
Oauth2 opaque tokens
Oauth2 self-contained
tokens
Mutual SSL
Basic Auth Config based supported,
can not plug user stores
API Keys

15. Feature Comparison
Feature API Microgateway API Gateway
SOAP backends
REST APIs
JMS backend
GraphQL API
GRPC Services
Web Socket API
Custom mediator
Advanced throttling
Schema validation
Jwt revocation
Per resource endpoints

16. API Manager & Microgateway 1/3

17. API Manager & Microgateway 2/3

18. API Manager & Microgateway 3/3
micro-gw init myproject
//add production endpoint api_definitions
micro-gw build myproject
//generate balx
RUN
gateway <fullpath>.balx micro-gw init myproject
micro-gw import <api_name> - v <version> myproject
micro-gw build myproject
//generate balx
RUN
gateway <fullpath>.balx

19. Microgateway configuration file

20. Conclusioni

21. Q&A?

22. GRAZIE!!!
Prossimo appuntamento:

23. Contatti
DOVE SIAMO
Milano - Torino - Padova - Roma
TELEFONO
Torino +39-011-0120371
EMAIL
wso2.sales@profesia.it
@