WSO2 Use Case - API Facade Pattern

1. WSO2 API Management Platform WebinarAPI Façade Pattern Asanka Abeysinghe - Director, Solutions Architecture, WSO2 © WSO2 2012. Not for redistribution. Commercial in Confidence. 2. API Management Platform Webinar Series 3. Source for my Business APIsWho is going to use my APIs ?Can I change my business / business processes ?Write new set of services ? What will happen to the oldservices ?Can I expose my services as it is? 4. Business Service Platforms- Heterogeneous- Styles- SOAP- RESTful- Bindings- SOAP/HTTP/s- POX/HTTP/s- POX/JMS- JSON/HTTP/s- File {CSV, EDA, COBOL}- Development languages {Java, WCF, PHP, C/C++, JavaScript}- Functionality{Focused on internal service consumers/ applications}- Silos, owned by various BUs, no control 5. Demand for APIsPicture Credit : http://www.newscientist.com/blogs/onepercent/2012/01/letting-gamers-experience-the.html 6. Demand for APIs – cont.. 7. Façade PatternPicture Credit : http://hypebeast.com/2009/11/nike-harajuku-store-opening/ 8. API Façade Pattern – cont.. External Format (Demand) FaçadeMediation Backend Services 9. API Façade Pattern – Generic PatternExternal Format (Demand)Façade Façade + MediationMediationBackend Services 10. Results- Brining complexity to the Façade layer {outside the firewall}- Writing wrapper service to shape the backend services- Few protocols {HTTP/s, JMS} cannot solve the complexityof integration- Service virtualization, chaining, orchestration, complexrouting requirements- Missing architecture decupling- Limitations to scale 11. WSO2’s API Management Vision- Create APIs- WSO2 ESB, Application Server, Data ServicesServer and BPS- Find and subscribe/buy APIs- API Store and Governance WSO2 API- Manage, secure and protect APIs Management- API Management and GatewayPlatform- Monitor and Monetize APIs- API Monitoring and Analytics- Develop, host and run API-based applications in aPlatform-as-a-Service- WSO2 App Factory- Domain Specific PaaS 12. Why? To be PRAGMATIC- Gap between the demand and current service platforms- Required to call multiple services to make a meaningful API method/verb- Required to call multiple data layers to build a resource / noune {MDM}- Required to update multiple systems / sub-systems {MDM, transactions}- Additional security due to external access {security bridging}- Additional business rules due to external access- Go to market 13. API Façade Pattern – WSO2 recommended architectureExternal Format (Demand)Façade Mediation MediationBackend Services 14. API Façade Pattern – WSO2 ImplementationExternal Format (Demand)Façade MediationBackend Services 15. API Façade Pattern – WSO2 Implementation extendedExt API Mediation / Service (Demand) Service Virtualization / PlatformsAPI FaçadeOrchestrationOther Service Containers 16. API Façade Pattern – WSO2 Implementation BIG PICTURE 17. WSO2 API Manager Platform – Component Architecture API Gateway API StoreAPI PublisherAPI Ext AuthAuth ServerAPI AnalyticsExt Load Balancer Ext LB Analytics2.0 PlatformBAM-2.0 Data Collector RDBMS (G-Reg +Analytics)2.0 BAM-2.0 Analytics + DashboardBAM-2.0 Data Store 18. Map API Façade to the Component Architecture- Invoke the API: API Gateway- Look-up, Subscribe : API Store- Govern, LCM : Publisher 19. API Publisher : LCM 20. API Publisher : Analytics 21. API Store : look-up/subscribe 22. Under the hood of API ManagerYou can combine theFaçade andMediation layers (ifrequired) and run as asingle architecturelayer. Picture Credit : http://green.autoblog.com/2011/07/28/four-cylinder-engines-dominate-in-u-s/ 23. How to ScaleCapacity Planning 24. Capacity Planning – Facts Matrix Component Capacity Planning Guidelines API Gateway Peak load of the API calls Auth Server Peak load of the API calls API Store Peak load of the subscriptions and browsing API Publisher Peak load of the API publishing and LCM tasks Analytics System load of the API calls 25. Deployment Pattern : Minimum with internal store 26. Deployment Pattern : Minimum with external store 27. Deployment Pattern : Extend to scale 28. Deployment Pattern : as an internal API solution 29. Summary- Clean architecture by separating the concerns- Have a clear separation of internal and external processing of an APIcall- Ability to scale based on the usage of each layer- Avoid implementing new services or building wrapper service layers- Leverage SOA principles with the new WEB API architecture- Utilize the middleware and go to market quickly 30. Future webinars on API Management 31. WSO2Con 2013 32. More Info Corporate website: http://wso2.com Solution Architecture Blog: http://wso2.com/blogs/architecture/ Business development team: [email protected] Asanka Abeysinghe  Blog : http://asanka.abeysinghe.org  Twitter : @asankama 33. lean . enterprise . middleware33