Gardient/behavioral-patterns
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Update readme

Browse Source
This commit is contained in:
Petrutiu Mihai
2016-07-13 14:41:54 +03:00
parent a9167c30e3
commit 7d013ce48b
1 changed files with 14 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
README.md
View File

@@ -321,10 +321,23 @@ The strategy pattern defines a family of algorithms, encapsulates each algorithm
* When you want to externalize part of the algorithm * When you want to externalize part of the algorithm
### c. Actors ### c. Actors
* Context -> Class that is using the strategy
* Strategy -> Strategy to be used by the context
### d. Pitfalls ### d. Pitfalls
* Client needs to be aware of the strategy, and be able to choose the strategy
* You might move the complicated decision of what to execute to the client out of the context.
### e. Flavors ### e. Flavors
* Classic -> Using separate class for each strategy
* Using Lambda -> Instead of having a class for each strategy, we could use lambda expression
### f. Examples ### f. Examples
* Shipping calculator: Starting class: ShippingCalculator.ShippingWithStrategyExample
* Decide what cost do I have if I want to ship a product via multiple shipping services
* Motivational Example starting class: ShippingCalculator.ShippingWithStrategyExample
* Arrange interview: Starting class: ArrangeInterview.Strategy.ArrangeInterviewExample
* Decide what should we do if we want to hire an employee, taking into consideration that it might be (dev, designer, tester, manager, devop),
depending on his experience he might be (junior, medium, senior, rockstar) and we might decide to hire him as (contractor, part time, full time)
* Motivational example: ArrangeInterview.ArrangeInterviewMotivationalExample
9. Template pattern 9. Template pattern
------------------ ------------------