wso2con asia 2016: api management strategies and best practices

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

●

○○○○

●○○○○

●

●

●

●

●●

●

●●

●●●●

○○○○

•

●

●

•

•

•

●●

●

Client / Partner

LDAP

Gateway

Key Manager

Store Publisher

Back EndJWT Token

JWT Token

{ "typ":"JWT", "alg":"RS256" }{ "iss":"wso2.org/products/am", "exp":1345183492181, "http://wso2.org/claims/subscriber":"admin", "http://wso2.org/claims/applicationname":"app2", "http://wso2.org/claims/apicontext":"/placeFinder", "http://wso2.org/claims/version":"1.0.0", "http://wso2.org/claims/tier":"Silver", "http://wso2.org/claims/enduser":"wso2User" }

•–

–•

●●

●

●

http://wso2.com/library/articles/2015/11/article-introducing-wso2-api-manager-new-rest-api-for-store-and-publisher-operations/

REST API Documentation page

https://docs.wso2.com/display/AM1100/apidocs/publisher/

Authentication Layer

Validation Layer

API Manager Implementation Layer

Exception Mapper

REST Service Implementation Layer

Response Flow Request Flow

Interceptor

Interceptor

Interceptor

CXF Container

Impl to API Model Mapper API to Impl Model Mapper

Service Stubs

Service Implementation

Swagger2CXF

Caching / Concurrency Control LayerInterceptor

●

●

●

●

1 2

3 3

4 5

Client / Partner

Back EndPublisherStoreGatewayKey Manager

WSO2CARBON_DB

WSO2AM_DB

Scale out

500 requests

500 X 4 requests

Scale upAPI authenticationMessage mediationService chaining

Message mediationService chaining

API authentication

Processing power 3 unit per request

Processing power 1 unit per request

Processing power 2 unit per request