Turn your SOA up to 11
•Download as PPTX, PDF•
0 likes•436 views
Learn the secrets of a successful Service Oriented Architecture from a seasoned veteran that has seen large scale implementations come and go with varying levels of success.
More Related Content
Similar to Turn your SOA up to 11
Similar to Turn your SOA up to 11 (20)
Recently uploaded
Recently uploaded (20)
Turn your SOA up to 11
- 1. 11
- 2. Jim Siegienski ~20 Years Experience Fortune 50 to Startups Enterprise Architect at Dave Ramsey (Lampo)
- 5. PROCESS
- 6. 3 Key Steps
- 7. Functional
- 9. Functional API
- 10. Review Functional API
- 11. Functional API Technical
- 12. Review Functional API Technical
- 13. Functional API Technical
- 14. Implementation
- 15. FUNCTIONAL
- 17. keep it simple
- 18. User Service Description: Represent a user in the system Create user Update user Get user Get current time Get favorite color
- 19. Business Unit Business Unit Service Business Unit Business Unit
- 21. API
- 23. Method: GET URI: /users/{key} Response: 200 Representation: { “first_name”: ”John”, “last_name”:”Doe” } Error: 400 Bad Request 401 Unauthorized 404 Not Found
- 24. A Noun is a Person, Plac e, or Thing.
- 26. GET Read POST PUT DELETE PATCH
- 27. GET POST Create PUT DELETE PATCH
- 28. GET POST PUT Update DELETE PATCH
- 29. GET POST PUT DELETE Delete PATCH
- 30. GET POST PUT DELETE PATCH Partial Update
- 31. Svc1 App2 Svc2 Security App1 Svcn
- 32. Permission ROLE Permission Permission Permission Permission
- 35. TECHNICAL
- 36. Flow Chart Class Diagram Sequence Diagram Data Model
- 37. Start Process Flow Chart Done? No Yes Start
- 38. Person FirstName LastName GetName() Class Diagram VIP User Username Importance Password GetImportance() Login()
- 39. Controller Service Model Sequence Diagram
- 40. Data Model person first_name last_name
- 41. IMPLEMENTATION
- 44. Controller Service Model
- 45. •No Business Logic •Take the Call Controller •Format the Output Service Model
- 47. Controller •Business Logic •Model Orchestration Service •Heart of the System Model
- 49. Controller Service •Data Access •As Fat as Possible Model
- 51. Who What Why? How
- 52. UI1 UI2 UI3 UIn App1 App2 Appn Svc1 Svc2 Svc3 Svc4 Svcn
- 53. Glory is fleeting, but obscurity is forever. Napoleon Bonaparte
- 54. Not Everything is black and white.
- 55. THANK YOU!
- 56. FURTHER READING
- 57. Books: SOA Governance by Thomas Erl Design Patterns: Elements of Reusable Object Oriented Software by GoF Expert One-on-One J2EE Design and Development by Rod Johnson Links: http://bestoked.blogspot.com/2012/02/restful-resources-required-reading.html http://www.springsource.org/ http://www.lucidchart.com/ Contact: jim.siegienski@gmail.com @JimSiegienski
Editor's Notes
- Functional - Keep it simple
- Functional - Limit scopeOne conceptDoes the capability belong here? Be honestDefine terminology
- Context free
- If you use the word "and" it's doing too much
- API - Clear, consistent, and concise-void tight coupling (RMI, RPC)
- API - REST - Resource as noun
- API - REST - Access via verb (method)Post, put, get, deletePatch?
- API - REST - Access via verb (method)Post, put, get, deletePatch?
- API - REST - Access via verb (method)Post, put, get, deletePatch?
- API - REST - Access via verb (method)Post, put, get, deletePatch?
- API - REST - Access via verb (method)Post, put, get, deletePatch?
- API - REST - Access via verb (method)Post, put, get, deletePatch?
- API - SecurityCentralize AuthorityTrust no-one
- Use permissions, not roles… pleasePermissions are granular and flexibleRoles are annoyingYou can grant Roles for administrative gains, but secure/check permissions (be specific)
- API - Versioning Accept headerAccept: application/vnd.lampo.service-v2+jsonDon't put versions in your URL! That will break the API
- API - Custom headers? We use some for tokens and error codes, need to do more evaluation
- Technical – documentationFlow chart, class diagram, sequence diagram, data model
- Simple flow chart top to bottom, left to right
- Simple class diagram
- Simple sequence diagram
- Simple data model
- Technical – ControllerKeep thin. Take call, respond to call. Separation of concerns
- Technical – ControllerKeep thin. Take call, respond to call. Separation of concerns
- Technical – ServiceIf using a thin model (cough, java) then have a thick serviceCross model orchestration.Heavy business logic if model is thin
- Technical – ServiceIf using a thin model (cough, java) then have a thick serviceCross model orchestration.Heavy business logic if model is thin
- Technical – ModelThin model (VO)Thick model (business) - works better in Ruby and other robust languages
- Technical – ModelThin model (VO)Thick model (business) - works better in Ruby and other robust languages
- Success is Fragile
- Not everything is black and white – ask what’s working and what’s not working?
- resources