Repository

Search…
Repository
Repository PHP
Repositories are used for retrieving and saving the aggregate to persistent storage. 
Aggregate need to be loaded in order to call method on it. 
Normally the flow for calling aggregate method, would looks like below. Which involves having handling service with access to repository.
1
class AssignWorkerCommmand
2
{
3
    private string $ticketId;
4
    
5
    private string $workerId;
6
    
7
    public function getTicketId() : string;
8
    {
9
       return $this->ticketId;
10
    }
11
    
12
    public function getWorkerId() : string
13
    {
14
       return $this->workerId;
15
    }
16
}
17
​
18
​
19
class CloseTicketHandler
20
{
21
    private TicketRepository $ticketRepository;
22
​
23
    #[CommandHandler]
24
    public function handle(CreateTicketCommand $command) : void
25
    {
26
       $ticket = $this->ticketRepository->findBy($command->getTicketId());
27
       $ticket->assignWorker($command->getWorkerId());
28
       $this->ticketRepository->save($ticket);    
29
    }
30
}
31
​
32
class Ticket
33
{
34
    public function assignWorker(string $workerId)
35
    {
36
       // do something with assignation
37
    }
38
}
Copied!
Ecotone provides possibility to mark Ticket Aggregate methods as CommandHandler directly. 
In that situation, Ecotone retrievies identifiers from Command message, pass them to Repository, calls the method on aggregate instance and saves it. In short it does code from CreateTicketCommand Handler for you. 
As Ecotone does not try to impose specific solutions, you are free to choose, which fits you best in specific context. Above example is based on External Command Handlers.
To get more details how to implement Aggregate, go to previous pages:
State-Stored Aggregate
Broken link
How to implement Repository
There are two types of repositories. One for storing State-Stored Aggregate and another one for storing Event Sourcing Aggregate.
Based on which interface is implemented, Ecotone knows which Aggregate type was selected.
The interface informs, if specific Repository can handle given Aggregate class.
You may implement 
Repository for State-Stored Aggregate
1
namespace Ecotone\Modelling;
2
​
3
interface StandardRepository
4
{
5
    
6
    1 public function canHandle(string $aggregateClassName): bool; 
7
    
8
    2 public function findBy(string $aggregateClassName, array $identifiers) : ?object;
9
    
10
    3 public function save(array $identifiers, object $aggregate, array $metadata, ?int $expectedVersion): void;
11
}
Copied!
1.canHandle method informs, which Aggregate Classes can be handled with this Repository. Return true, if saving specific aggregate is possible, false otherwise.
2.findBy method returns if found, existing Aggregate instance, otherwise null. 
3.save method is reponsible for storing given Aggregate instance. 
​
$identifiers are array of @AggregateIdentifier defined within aggregate.
$aggregate is instance of aggregate
$metadata is array of extra information, that can be passed with Command
$expectedVersion if version locking by @Version is enabled it will carry currently expected version
Repository for Event Sourced Aggregate
1
namespace Ecotone\Modelling;
2
​
3
interface EventSourcedRepository
4
{
5
    public function canHandle(string $aggregateClassName): bool;
6
    
7
    1 public function findBy(string $aggregateClassName, array $identifiers) :  EventStream;
8
​
9
    2 public function save(array $identifiers, string $aggregateClassName, array $events, array $metadata, int $versionBeforeHandling): void;
10
}
Copied!
Event Sourced Repository  instead of working with aggregate instance, works with events. 
1.findBy method returns previously created events for given aggregate. 
2.save method gets array of events to save returned by CommandHandler after performing an action
Event Sourcing Aggregate
Dispatching Commands
Last modified 7mo ago
Export as PDF
Copy link
Contents
How to implement Repository