StrataForge

Current selection

2 of 3 selected

You can now review the differences across the comparison table below.

Chain of Responsibilitybehavioral
View Remove
Flyweightstructural
View Remove

Criteria	behavioralChain of ResponsibilityView pattern	structuralFlyweightView pattern
Basics
Category	behavioral	structural
Summary	Pass a request through a sequence of handlers until one handles it or the chain ends.	—
Intent	Pass requests along a chain of handlers until one of them handles the request or the request reaches the end of the chain.	Use sharing to support large numbers of fine-grained objects efficiently by separating shared intrinsic state from per-object extrinsic state.
Decision factors
Problem	A request must pass through multiple possible handlers, but the sender should not need to know which handler will process it.	A system creates a large number of similar objects, but storing all of their state separately uses too much memory.
Tradeoffs	Requests can become harder to trace because control flows through multiple handlers. A long chain may add overhead if many handlers are checked on every request. It keeps handler logic isolated and easier to extend.	Adds complexity because state must be split into shared and unshared parts Can be harder to understand when many objects depend on an external context
Practical fit
Languages	typescript java python angular react react-native csharp dotnet	typescript java python angular react react-native csharp dotnet
Platforms	frontend backend integration	Web Backend Mobile UI kits Cross-platform systems
Integration notes	Chain of Responsibility is useful for validation pipelines, support routing, approval flows, and any system where requests may be processed by different handlers in sequence.	Flyweight is useful when thousands or millions of similar objects need to be represented efficiently, such as trees, glyphs, tiles, or UI tokens.