Download to read offline
Uploaded byPer Ökvist
Self contained systems - In practice
The document discusses the concept of self-contained systems (SCS), advocating for the separation of functionality into independent systems that collaboratively form a logical whole. It emphasizes the need for each SCS to include both data and logic to implement meaningful features and promotes asynchronous communication between systems. The architecture allows for the dynamic composition of web pages using fragments, enabling efficient caching strategies and integration across multiple websites.
Self contained systems - In practice
- 1. Self contained systems inpractice PER ÖKVIST, @per_okvist
- 3. THEORY WHAT IS SELFCONTAINED SYSTEMS?
- 4. Function Aggregate Boundedcontext
- 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 aseparation 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 mustinclude 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 otherSCSs or 3rd party systems is asynchronous wherever possible.
- 20.
- 21. THINK – multipleweb 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
- 23.
- 24.
- 25. Pages and fragments “Teams shouldpublish a catalog of their fragment types and fragment instances”. Pages Fragment OWNS SHARES Fragment
- 26. SCS / Vertical A Self-Contained-System couldbe part of a larger system, thus often referred to as a Vertical Pages Fragment Fragment Backend(s) Vertical
- 27. Transclusion Compose pages byincluding 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 theinclusion 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.
- 30.
- 31.
- 32.
- 33. Transclusion - Contextneutrality http://microservice-websites.netlify.com/ <esi:include> <h-include> Gustaf Nilsson Kotte – Microservice web sites
- 34.
- 35.
- 36. Multiple sites A sitemade 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.
- 41.
- 42.
- 44.
- 45. - Procedures - Views -Projections - Composition Read models
- 46. CDN – WithESI support “infinite” Cache-Control: max-age=<seconds>
- 47.