Self contained systems - In practice
•Download as PPTX, PDF•
0 likes•674 views
How to build a system of systems. How could we avoid a large monolithic system, utilizing a set of smaller systems in collaboration? The idea is to break a large system apart into several smaller self-contained systems or SCSs, that follow certain rules. A SCS is owned by a team, with all data and logic needed and makes features available via it’s own UI. This favors asynchronous communication and UI composition. In this talk we’ll introduce SCS and it’s background, and venture in to how we use this an approach within an e-commerce solution.
Recommended
More Related Content
Similar to Self contained systems - In practice
Similar to Self contained systems - In practice (20)
Recently uploaded
Recently uploaded (20)
Self contained systems - In practice
- 1. Self contained systems in practice PER ÖKVIST, @per_okvist
- 3. THEORY WHAT IS SELF CONTAINED SYSTEMS?
- 4. Function Aggregate Bounded context
- 10. https://speakerdeck.com/stilkov/microservices-patterns-and-antipatterns-1?slide=40 https://www.youtube.com/watch?v=VaYmRe104HU Stefan Tilkov - Microservices Patterns and Anti-patterns
- 11. Cohesion “Focus on a separation of the functionality into many independent systems, making the complete logical system a collaboration of many smaller software systems”
- 14. ”We love monoliths – so let’s build a lot of them!” S. Tilkov.
- 18. Data “Each SCS must include data and logic. To really implement any meaningful features both are needed. An SCS should implement features by itself and must therefore include both.”
- 19. Communication with other SCSs or 3rd party systems is asynchronous wherever possible.
- 21. THINK – multiple web sites Self Contained System. The idea is to break a large system apart into several smaller self-contained systems, or SCSs, that follow certain rules.
- 22. Multiple sites / Self Contained Systems
- 24. Composition
- 25. Pages and fragments “Teams should publish a catalog of their fragment types and fragment instances”. Pages Fragment OWNS SHARES Fragment
- 26. SCS / Vertical A Self-Contained-System could be part of a larger system, thus often referred to as a Vertical Pages Fragment Fragment Backend(s) Vertical
- 27. Transclusion Compose pages by including fragments, on the server or on the client, enabling a greater cache strategy as well. SSI : Server side include – good for static content CSI : Client side include – good for dynamic / personalized content
- 28. Transclusion is the inclusion of part or all of an electronic document into one or more other documents by hypertext reference. The result of transclusion is a single integrated document made of parts assembled dynamically from separate sources, possibly stored on different computers in disparate places.
- 29. IN PRACTICE
- 30. Composition
- 33. Transclusion - Context neutrality http://microservice-websites.netlify.com/ <esi:include> <h-include> Gustaf Nilsson Kotte – Microservice web sites
- 35. Layout Page baseline header footer Search Catalog Checkout
- 36. Multiple sites A site made of sites.
- 37. /products /support Gateway - YourSite.com YourSite.com/products
- 38. /products /support Gateway - YourSite.com YourSite.com/products CDN – With ESI support
- 39. Gateway - YourSite.com CDN – With ESI support Account My Pages Search Catalog Product Details Checkout Support
- 40. Vertical/App
- 42. Data
- 44. Caching
- 45. - Procedures - Views - Projections - Composition Read models
- 46. CDN – With ESI support “infinite” Cache-Control: max-age=<seconds>