Event driven architectures for eCommerce Integration
•
0 likes•306 views
This session will discuss the event-driven architectural patterns and practices leveraged in recent eCommerce projects utilising MuleSoft and Solace. Discussing what works well and lessons learned along the way, finishing up with a demo of event-driven async API’s combined with mobile protocols like MQTT.
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Event driven architectures for eCommerce Integration
Similar to Event driven architectures for eCommerce Integration (20)
More from Nikolai Blackie
More from Nikolai Blackie (10)
Recently uploaded
Recently uploaded (20)
Event driven architectures for eCommerce Integration
- 1. Event Driven Architecture for eCommerce Integration Dragos Buleandra Nikolai Blackie MuleSoft Meetup - September 2020
- 2. What we’ll talk about today Drivers, Inhibitors & Enablers Standards, Patterns & Reference Architecture Demo, Lessons Learned & Questions
- 3. • MuleSoft leveraged for API enablement and integration • Solace PubSub+ Event Broker leveraged for multi protocol eventing, event mesh and messaging • Implemented API Led/Event Driven architecture to support Covid contactless eCommerce solutions using Salesforce, SAP Hybris and internal systems • Finalists for Digital Transformation of the year and Designers institute Best Design Awards • In 54 days since launch • 10k+ Downloads • 2k+ Orders • $1m+ Revenue
- 6. Technical Inhibitors and Enablers Monolithic Architectures Legacy Systems Tight Coupling Slow Release Cycles Inability to Scale Cyber Security Secure by DesignScalable Hybrid Cloud CI, CD and DevOps Practices Event Driven Architecture API Led Architecture
- 8. Standards for EDA and APIs
- 9. Standards for EDA – Cloudevents.io { "id":"f637689b-bfbf-4456-88f7-d0896e097f2f", "source":"io.choria.machine", "specversion":"1.0", "subject":"example.net", "time":"2019-12-05T09:37:45Z", "type":"io.choria.machine.watcher.exec.v1.state", "data":{ "protocol":"io.choria.machine.watcher.exec.v1.state", "identity":"example.net", "id":"bac83cb2-2a37-460b-9c7a-633c6286bff5", "version":"0.0.1", "timestamp":1575538665, "type":"exec", "machine":"DockerExample", "name":"monitor", "command":"./monitor.rb", "previous_outcome":"success", "previous_run_time":1387005527 } }
- 10. Common Integration Patterns Request/Response & Request/Reply Consumer Consumer Provider Request ResponseReciever Async Reply Provider Request ResponseSync Response
- 11. Common Integration Patterns One Way Guaranteed Delivery Consumer Provider Subscriber API JMS Pub JMS Sub 200 OK
- 12. Common Integration Patterns Guaranteed Delivery with Async Response Consumer Provider Subscriber API Pub Sub MQTT JMS REST
- 13. eCommerce Reference Architecture ERPPIM V PIM Events Order Events IDM Events CIM Master Data Place Order Stock/Pricing Order Request Stock/Pricing MQTT Notifications REST RequestsCIM CIM Events
- 14. Less Talk, More Demos Demo, Lessons Learned, Questions
- 15. Demo Use Case – Event Driven Order Fulfillment Consumer Provider Fulfilment API Pub JMS Sub JMS MQTT REST Pub JMS Order System API
- 16. Lessons Learned • Networks are flaky • Choose MQTT client ids carefully • Leverage standards for events • Establish standard patterns and templates • Architectures will continuously evolve
- 18. References • https://blogs.mulesoft.com/dev/design-dev/moving-from- restful-to-eventful/ • https://blogs.mulesoft.com/dev/api-dev/design-message- driven-and-event-driven-apis/ • https://raml.org/ • https://github.com/OAI/OpenAPI-Specification • https://cloudevents.io/ • https://www.asyncapi.com/ • https://solace.com/blog/event-driven-kotlin-android-app- mqtt-solace-pubsub/ • https://mqttfx.jensd.de/ • https://www.ciosummit.co.nz/awards/finalists • https://bestawards.co.nz/digital/digital- products/apolinar/Entry:90943c1a-9b8c-41cf-88a2- f91a173dad5c/