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.
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”
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.”
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.
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.