SOA Doing Right
Download as PPTX, PDF0 likes1,579 views
In this CAKE LABS Innovation Session, Chamin and Daham present “Doing SOA Right”. Microservices is all about service oriented architecture (SOA) done right, and has become the latest buzzword in the global IT arena. The inherent issue with Microservices in traditional SOA is that when a particular service fails, it affects the other services inherently, thus crippling the entire system. This traditional monolithic architecture defines a single software application which bundles all the features and is deployed.
More Related Content
What's hot (20)
Viewers also liked (7)
Similar to SOA Doing Right (20)
More from Schezarnie Racip (8)
Recently uploaded (20)
SOA Doing Right
- 3. WTC • ONE electricity supply • ONE water supply • ONE elevator
- 4. Monolithic Architecture • Single SW application with ALL functionalities implemented/deployed • Each floor a dedicate service (HR, Marketing ++) • Monolithic SOA • Coarse-grained (depend on others. Eg. Shipping service waiting for approval from Admin service) • Wider scope (manages many business cases) • Complex message formats Monolithic Architecture : Layered Architecture
- 5. Monolithic Architecture Shipping : API Logic Dao
- 6. 98 Acres • OWN refrigerator • OWN water supply • OWN power generator • Tiny bit services are bundled CAN function INDEPENDANTLY
- 7. Microservices Architecture Online retail store : ebay
- 8. Microservices • Microservice • Develop single application • Fine-grained manner • Independent of other services • Deploy independently • Misconceptions • Line of Codes • “Micro” (how small it is :O) • Team Size
- 9. Design Consideration • Single Responsibility Principle(SRP) : limited and focused business scope. (IMPORTANT : righted sized services) • Service boundaries + business capabilities • Microservices = few Operations/Functionalities, simple Message Formats • Evolving process – Micro service might decomposed into future.
- 10. Messaging in Microservices • Monolithic Architecture • Function calls/ Language level methods • SOA : SOAP, WS* with HTTP, JMS ++ • ESB • Micro Services • Simple • Light weight • ESB Killer
- 11. Messaging in Microservices • Synchronous Messaging • Client waits for response from service • REST, Thrift • Async Messaging • NO or least expect a response • Light weight • AMQP, MQTT, STOMP
- 12. Integrating Microservices • ESB Killer • Monolithic SOA – client connections are forward to different APIs • Microservices do not use ESB (different wiring mechanism) • Microservices • Smart Endpoints – Moves business logic to services and clients • Dumb pipes – To connect services
- 13. Integrating Microservices • Point to Point – Invoke service directly
- 14. Integrating Microservices • API Gate-Way style
- 15. Integrating Microservices • Message Broker style Micro service can publish it’s service, as well as subscribe to services of others
- 16. Deployment & Orchestration • Each MS – deploy as separate Docker(to deploy services) image • Scaling - # of containers • Early days – minor change in one, deploy total • Kubernetes - #Google (Stratos) • Orchestration
- 18. Pulse Security • Salesforce Authorization • Federated authorization • OAuth • Pulse Agent • Which POS Device
- 19. Microservices Security • Central user repository store • OAuth 2.0 • Authorization • Token Sharing • OpenId Connect • Authentication • OAuth + ID token (user info)
- 20. Daham
- 22. Is Node.js Really Single Threaded?
- 23. Is Node Actually Single Threaded?
- 24. Possible Task Strategies • Possible Task Strategies • Foreground (In-line) • Parallel • Local Messages (Forking) • Queues
- 25. Foreground (in-line) caterRequest (req, res, next) { doTask(function(err, data) { if (err) { return res.send(‘fail'); } else { return res.send(’success'); } }); }
- 26. Foreground (in-line) • Good side • Gives chance to other requests. • Bad Side • Using server resources to other tasks (e.g. email sending, AWS calls) • Timeout to client for partially success.
- 27. Parallel caterRequest(req, res, next) { doTask(function(err, data) { }); return res.send(’success'); } Just ignore the callback
- 28. Parallel • Good side • Very fast. • No extra codes needed for thread life cycle manipulation. • Bad Side • 0 callbacks 0 data. No idea about what happened.
- 30. Local Messages (Forking) • Good side • Web server process is completely independent of task process.(i.e. email sender , AWS caller) • Error handling, throttling and retrying can be achieved. • Bad Side • Only suitable for single host environment.
- 31. Queues
- 32. Queues
- 33. Advantages of Queues • Decoupling work producers and work consumers • Making retry logic easier to implement • Distributing work load throughout time • Distributing work load throughout space (nodes) • Making asynchronous work • Making external systems easier to integrate
Editor's Notes
- #2: Is it really necessary to say company presentation here?
- #5: OFFICE PICS.
- #6: Layer fails, all the other services are also failing.
- #7: When a default occurs, it affects only the corresponding cottage
- #8: Let’s take a real world example of Microservices can be applied
- #9: OFFICE PICS.
- #10: SRP : only about one single tiny business logic. -> doesn’t mean small (always) That’s why I emphasized it’s a bit vague misleading term.
- #11: Frist, let’s give a little though on how : traditional SOA, or the Monolithic Architecture perorms messaging.
- #12: In comparison to synchronous messaging, where client waits for service response, in Async messaging, client doesn’t wait for response,
- #13: Duty of the ESB to perform the wiring mechanism of services For a huge system to work, our famouse example Ebay to work, Each deployed micro service need to interact with outher micro services. ======================== You might think that, this is very cumbersome simply by looking at this, It’s not so. Microservices offers diversified approaches in integrating independent microservices
- #14: What is the big fat question , When a client tries to invoke a service, directly, there can be vagues ways of invoking the service between them. So it is not encourage follow this approach eventhough, this is an integration pattern, So what would be the solution
- #15: Here, the clint directly connects with the api gateway and API gateway manages the process of matching corresponding microservices to clients’s request
- #16: Each micro service can publish it’s service, as well as subscribe to services of others
- #17: Each micro services can deploy as separate docker image
- #18: Governance and security are two major aspects in services. In monolithic approach , we have to establish security and governance considering entire system., which is a complex dea Also chances are high for loop holes.
- #19: OFFICE PICS.
- #20: OFFICE PICS.