The Clean Architecture in php

class
BillingService
{
protected
$orderRepository
;
protected
$invoiceRepository
;
protected
$invoiceFactory
;
public function
__construct
(
OrderRepositoryInterface
$order
,
InvoiceRepositoryInterface
$invoice
,
InvoiceFactory
$factory
) {
$this
->
orderRepository
=
$order
;
$this
->
invoiceRepository
=
$invoice
;
$this
->
invoiceFactory
=
$factory
;
}

---

Database Independence
89
public function
generateInvoices
(\DateTime
$invoiceDate
) {
$orders
=
$this
->
ordersRepository
->
getActiveBillingOrders
(
$invoiceDate
);
foreach
(
$orders
as
$order
) {
$invoice
=
$this
->
invoiceFactory
->
create
(
$order
);
$this
->
invoiceRepository
->
save
(
$invoice
);
}
}
}
This service is pretty simple, because it leverages the power of the
OrderRepository
given to it to
retrieve orders, and the
InvoiceFactory
to generate invoice objects. It then simply persists them
to the database using the
InvoiceRepository
. The
BillingService
can now be used anywhere
that invoices need to be generated for whatever means of ordering the system needs implement.
This is abstracted away into the service, so that the code is not repeated all over the place.
Further, this code does not depend on a specific data store whatsoever, instead, asking for an
implementation of both
OrderRepositoryInterface
and
InvoiceRepositoryInterface
. If those
dependencies are satisfied with concrete implementations, the Service works correctly finding
orders to invoice and generating those invoices.
This code is powerful, but dead simple. It’s coupled to nothing but the rest of our Domain Model
and Domain Services layer. It is 100% decoupled from any specific database implementation.