API-first Integration for Microservices
0 likes326 views
The document discusses the concept and evolution of microservices architecture, emphasizing the importance of API-first integration for developing reusable business capabilities. It features a case study of Juma Market, illustrating how microservices facilitate online grocery ordering through various customer and internal services. Key takeaways highlight the role of API management, containerized microservices, and the ability to mediate existing systems in a heterogeneous environment.
![JuMa Market Services - Customer APIs – New Order
Payload
{"clientid" : "87-631-8815",
"amount": "127", "iban" : "FR61 2364 7700 85E5 PVMQ 1IVH 463",
"articles": [
{
"itemnumber": "g7551-90iq66",
"number": "1“ },
{
"itemnumber": "o3854-925c51",
"number": "1" },
{
"itemnumber": "h9811-56bg00",
"number": "1" }
]
}](https://image.slidesharecdn.com/api-firstintegrationformicroservicesprefinalforwso2-minus-video-200528150114/85/API-first-Integration-for-Microservices-20-320.jpg)
API-first Integration for Microservices
- 1. API-first Integration for Microservices Kasun Indrasiri Senior Director - Integration Architecture @ WSO2 Rob Blaauboer WSO2 Trainer and Integration Consultant @ Yenlo
- 2. WSO2 and Yenlo – decade long partners WSO2 Founded in 2005, WSO2 enables the composable enterprise. Our open- source, API-first, and decentralized approach helps developers and architects to be more productive and rapidly build digital products to meet demand. Yenlo Founded in 2007, Yenlo is the leading, most experienced, Platinum Value-Added Reseller of WSO2, acting and delivering first class integration services on a global, worldwide level, with a strong focus on digital transformation.
- 3. About the presenters Kasun Indrasiri Senior Director – Integration Architecture, WSO2 Rob is Integration Consultant and WSO2 Trainer with more than 35 years IT experience. In addition to his work, he is an active blogger working on a number of articles in which he talks about WSO2 components and their purpose especially aimed at non-technical readers. Kasun is the senior director of Integration Architecture at WSO2, and an architect with over nine years of experience in enterprise integration and microservices. He is an author and an evangelist on microservices architecture. He has authored the books 'Microservices for Enterprise' (Apress: 2018 Q4) and 'Beginning WSO2 ESB' (Apress – Released in 2017). He was also an architect and the product lead of WSO2 ESB and a committer/PMC member of the Apache Software Foundation. He has founded the Silicon Valley Microservice, APIs, and Integration Meetup, a vendor-neutral microservices meetup in the San Francisco Bay area. Rob Blaauboer WSO2 Trainer & Integration Consultant, Yenlo
- 4. What is Microservices Architecture? ● The foundation of MSA is about developing a single application as a suite of fine- grained and independent services running in its own process, developed and deployed independently.
- 5. Evolution of Microservices ● Monolithic Applications Application 2 Application 1 Application 3 Application 4 Consumers
- 6. Evolution of Microservices ● API Management and SOA Consumers ESB System Service 1 Service 2 Service 3 Service 4 Service 5 API Management Application server
- 7. Evolution of Microservices ● Breaking the Monolith… Web Portal Mobile Apps Store Admin Web Storefrons Promotion Mgmt API Management Product Details Shopping Cart Order Mgt Payment Proc. Payment Proc. Customer Mgt. Account Mgt Order Tracking Financial Mgt Fraud Detection Tax Mgt Inventory Mgt Allocation-Release Self-Service Giftcards Promotions Pricing Subscription Credit service CRM Mgt Shipping Data Warehouse Finance System Shipping Inventory Payment Gateway Cloud Services E.g. Salesforce, Paypal etc
- 8. Breaking the monolithic integration ● Smart endpoint and dumb pipes
- 9. What is API-first Integration? ● The process of building reusable business capabilities by connecting services, systems and data, and offer them to consumers via APIs.
- 10. API-first Integration Styles ● Top-Down : Start from APIs ○ Begins with API design for the business capability. ○ Integrations are created as part of the API implementations.
- 11. API-first Integration Styles ● Bottom-Up : Start from API implementation/Integrations ○ Begins with building integration for the corresponding business capability. ○ Then expose that integration as an API at the API Gateway.
- 12. API Gateway API-first integration for microservices API Service P API Service Q API Service R API Service S Consumers μ Service A Event Broker Proprietary & Legacy Systems Web API / SaaS API Services/ Edge Services Composite Service/ Integration Services Core Services/ Atomic Services μ Service I μ Service H μ Service J μ Service E μ Service C μ Service D μ Service G μ Service B API Management μ Service K
- 13. API Gateway API-first integration for microservices API Service P API Service Q API Service R API Service S Consumers μ Service A Event Broker Proprietary & Legacy Systems Web API / SaaS API Services/ Edge Services Composite Service/ Integration Services Core Services/ Atomic Services μ Service I μ Service H μ Service J μ Service E μ Service C μ Service D μ Service G μ Service B API Management μ Service K
- 14. API-first Integration for Microservices with WSO2
- 15. Use Case JuMa Market Online Groceries
- 16. JuMa Market, a local supermarket chain wants to start with online ordering for instore pickup and delivery to the home. This has always been one of their goals but the current situation with Covid19 makes it more urgent. The APIs JuMa has created a number of micro services divided into two categories: ● Customer services (new client, order groceries, change order etc.) ● Internal services (add articles, add suppliers, order picking etc.) Use Case : Online ordering, delivery and pickup
- 17. JuMa Market Setup The setup for JuMa Market is an API Manager as a front to a Kubernetes based Micro Integrator offering micro services. API Manager front for developers Micro Integrator microservices Payment provider Stripe (mocked) Mail service mocked Supplier Order mocked Restock mocked
- 18. Some JuMa Market Services Customer APIs ● Add new client ● Change client ● Order groceries ● Change order Internal APIs ● Add supplier ● Add article ● Get picklist ● Reorder ● Receive shipment ● Restock
- 19. Example JuMa Market Services - Customer APIs Add new client ○ Context client ○ Resource /new ○ HTTP verb POST Change client ○ Context client ○ Resource /change ○ HTTP verb PUT Order groceries ○ Context order ○ Resource /new ○ HTTP verb POST Change order ○ Context order ○ Resource /change ○ HTTP verb PUT
- 20. JuMa Market Services - Customer APIs – New Order Payload {"clientid" : "87-631-8815", "amount": "127", "iban" : "FR61 2364 7700 85E5 PVMQ 1IVH 463", "articles": [ { "itemnumber": "g7551-90iq66", "number": "1“ }, { "itemnumber": "o3854-925c51", "number": "1" }, { "itemnumber": "h9811-56bg00", "number": "1" } ] }
- 21. JuMa Market Services - Customer APIs - Add new client Payload { "id" : “12-345-6789" "firstname" : “Jan", "lastname" : “Doe", "email" : “jdoe@w3.org", "gender" : "Male", "streetaddress" : "20982 Ruskin Place", " city": "Yevlakh", "iban" : "BA77 0884 5374 5154 4900", "balance": 383}
- 22. Use Case Order Service Order service receives an order, consisting of client identification and repetitive element that has the order and the quantity of each order item in it. Via Payment service the account of the clients is charged. Pick Service Pick Service retrieves the order from the queue and sorts the order items based on aisle and area for the order person to pick. When the order is picked the quantity is deducted from the in stock count. If the quantity falls below a certain minimum a message for reordering is put on a queue. At the end of the day the orders are sent out. Restock service The restock queue will be read at the end of the day and a list will be compiled and send to distributors / manufactures. Notification The client is notified in case of a pick or gets a confirmation in case of delivery.
- 23. Use Case Order Send order Receive Payment required On queue Pick Order Pick list Order readyClient ReorderPayment failed Group 1 : Receive, Pay and Queue Group 2: Pick and Reorder Group 3 : Notify Client
- 25. API Manager Developer Portal
- 26. Order API
- 27. Payment API
- 29. Receiving emails
- 30. DEMO
- 31. Q & A Time for questions and answers!
- 32. Key take aways ● API-first integration allows you to build reusable business capabilities by connecting services, systems and data, and offer them to consumers via APIs. ● The API Manager is the gatekeeping frontend to your microservices enabling management, monitoring and security ● Containerized Micro services allow you to quickly add or remove capacity depending on demand ● In a heterogenous landscape, mediation and transformation enable you to create microservices that interact with existing systems
- 33. Want to know more about API-first Integration or microservices? Reads our blogs on : ● https://blog.wso2.com ● https://www.yenlo.com/blog Read our whitepapers ● https://wso2.com/whitepapers/ ● https://www.yenlo.com/white-papers