The Clean Architecture in php

Strategy Pattern
The Strategy Pattern allows the behavior of an algorithm to be determined during runtime of
an application. Strategies are usually a family of classes that share a common interface, that each
encapsulate separate behavior that can be interchangeable at runtime.
Let’s say we need to develop an invoicing process for our customers, who have the option of
choosing between two methods of receiving their invoices: email or paper.

---

Design Patterns, A Primer
28
public function
invoiceCustomers
(
array
$customers
) {
foreach
(
$customers
as
$customer
) {
$invoice
=
$this
->
invoiceFactory
->
create
(
$customer
,
$this
->
orderRepository
->
getByCustomer
(
$customer
)
);
// send invoice...
}
}
Our
InvoiceFactory
takes care of generating an invoice from all the orders returned by our
OrderRepository
, so how do we go about sending those invoices?
Using the Strategy Pattern, we first define an interface that describes how all invoices should be
sent, regardless of delivery method: