See http://verraes.net/2013/09/sensible-interfaces/ for the argumentation. Note that most components are already using a descriptive name for the provided implementation rather than making it the priviledged one (for instance class SimpleEventBus implements EventBusInterface)

Doing such should be done quickly, to avoid fighting with BC concerns with the current interface names.

Sorry if this is a silly question and I am missing something.

Since the same table is used for all events in the event store: if I have two aggregates classes and I call EventSourcingRepository::load() on a repository for one aggregate class with an id belonging to an instance of the other aggregate class then there is no exception. Instead the events are played back against the wring type of entity and silently do nothing as there are no methods to handle them.

Am I (a) doing something wrong to make this possible at all (b) missing something that should make this throw an exception (c) just needing to implement something that stops this within my aggregates?

Introducing support of MongoDB as EventStore.

Features included in this PR:

• read queries against primary nodes for strong data consistency
• read committed isolation level to avoid reading partial event commits
• test cases adopted for MongoDB

I have created several projections/read models and stored those in ElasticSearch using the ElasticSearch repository. Afterwards I decided to move the read models into another namespace and now the serializer fails because the class does not exist.

I have traced the issue to this location: https://github.com/qandidate-labs/broadway/blob/master/src/Broadway/Serializer/SimpleInterfaceSerializer.php#L47

Because this is a dev environment I have emptied my ElasticSearch instance and it works again so I am afraid I can no longer capture additional information but I hope this report helps to resolve this issue. I can imagine that during a refactoring this can also happen in a production environment.

It would be nice to have a component that can replay all events from an event store (in historical order) to an event bus. This would facilitate a few use cases, like:

• correcting faulty read models
• initialize new read models

We've already coded a callable class EventStream specific for DBAL (https://github.com/cultuurnet/udb3-php/commit/9af9770ca1bfa3976f977f802cb85a0f05d0132f) which returns a PHP Generator for iterating over all stored events in the right historical order, and it's used in a CLI command in our SIlex application (https://github.com/cultuurnet/udb3-silex/blob/feature/event-stream-replay/src/Console/ReplayCommand.php#L47). Unfortunately we had to copy quite some code from the DBAL EventStore to our class. Splitting up some methods like deserializeEvent() from the DBALEventStore to a separate class might be a good idea, or the EventStore interface itself could be extended to allow to retrieve all events. There are several possibilities. I'd be happy to discuss this a bit more with you.

I will start working on a broadway integration for Laravel this week / month. Should I create a separate repository or, make a pull request once it's finished?

In this PR I have so far fixed the following problems:

• Previously there was no way to register saga's automatically. I've added the RegisterSagaCompilerPass for this and you can use the broadway.saga service tag now.
• Saga instances should be provided as the second argument of the MultipleSagaManager, for which there was no service definition yet. I've added it.
• The SagaScenarioTestCase didn't conform to the other *TestCase classes in this library in that you had to create your own scenario. I changed this: it's now created for you. Since a saga is likely to use generated UUIDs, a sequence generator for them has been provided, so this allows you to provide a fixed set of UUIDs before running your test by calling setGeneratedUuids(). I have modified the API of the MockUuidSequenceGenerator to make this possible.
• Add a saga example, point to some references.
• Add a comment about the service tag.

Looking forward to your feedback!

This is a start to add the stream type (in most cases the Aggregate Root) to the EventStore.

Still TODO:

• [ ] Check if we need to normalize the classname
• [x] Update CHANGELOG
• [ ] Give some hints/snippets to add a migration to your application
• [x] Provide a more sensible name, I don't really like stream type here

Hi,

I was searching via findBy method https://github.com/qandidate-labs/broadway/blob/41a495d69fba2303622febfb3bc715a0f500c61d/src/Broadway/ReadModel/ElasticSearch/ElasticSearchRepository.php#L91 and was not getting any results.

$fields = [
    'name' => 'beta',
];
$this->repository->findBy($fields)

I tried with plain elastic search api and results are getting for below api .

<?php
$searchParams = array();
$searchParams['index'] = 'something';
$searchParams['type']  = 'Some\Namespaced\Class';
$searchParams['body']['query']['wildcard']['name'] = 'b*';
// $searchParams['body']['query']['match']['name'] = 'beta';

The find with id is working as expected.

Thanks!

This is a little strange, and it's likely an issue with how I'm using Doctrine DBAL. But, other users of this library may run into this issue, and it would be helpful if there's an answer here.

Everything works just fine if I use pdo_sqlite. The problem comes in when using the pdo_pgsql driver. There's apparently some column name case-sensitivity issues happening and I cannot figure out the way around it. Granted, I'm new to working directly with DBAL, but still... nothing I've tried helps.

I have a test class with the following set up:

$parameters = [
    'driver'        => 'pdo_pgsql',
    'user'          => 'test',
    'password'      => 'test',
    'database'      => 'test',
    'host'          => 'localhost',
    'port'          => 5433,
];

$connection     = DriverManager::getConnection($parameters);
$schemaManager  = $connection->getSchemaManager();
$schema         = $schemaManager->createSchema();
$eventStore     = new DBALEventStore($connection, new SimpleInterfaceSerializer(), new SimpleInterfaceSerializer(), 'events');

if ($table = $eventStore->configureSchema($schema)) {
    $schemaManager->createTable($table);
}

Yes, 5433 is the correct port on this machine (not the default 5432) and all of the connection info is correct. I can connect to the database.

Here's the problem:

When createTable($table) is called, the column names are getting normalized and thus lowercase. This is an issue with the recordedOn field. The column name is getting created as 'recordedon'. This means that the deserializeEvent is throwing an error on

DateTime::fromString($row['recordedOn'])

because it thinks the recordedOn doesn't exist (which it doesn't the database has it as 'recordedon').

The inserts into the table work just fine. The data is getting retrieved just fine. It just crashes in the deserializeEvent method.

If I manually change the column name in the database to recordedOn, then the insert commands in the event store no longer work.

Broadway\EventStore\DBALEventStoreException:

Caused by
Doctrine\DBAL\DBALException: An exception occurred while executing 'INSERT INTO events (uuid, playhead, metadata, payload, recordedOn, type) VALUES (?, ?, ?, ?, ?, ?)' with params ["07ebf76f-7ddf-4e57-969d-e271c560ebdd", 0, "{\"class\":\"Broadway\\\\Domain\\\\Metadata\",\"payload\":[]}", "{\"class\":\"Cybernox\\\\Theme\\\\Events\\\\ThemeCreatedEvent\",\"payload\":{\"themeId\":\"07ebf76f-7ddf-4e57-969d-e271c560ebdd\"}}", "2014-09-16T07:07:02.626363+00:00", "Cybernox.Theme.Events.ThemeCreatedEvent"]:

SQLSTATE[42703]: Undefined column: 7 ERROR:  column "recordedon" of relation "events" does not exist
LINE 1: ...T INTO events (uuid, playhead, metadata, payload, recordedOn...

I thought it might be simply a case of needing to configure the connection to use the PDO::CASE_NATURAL values, so I added a driverOptions to the connection. Still nothing (trying CASE_LOWER and CASE_UPPER didn't work either. In fact, UPPER caused a bigger crash where tables and column names were empty)

$parameters = [
    'driver'        => 'pdo_pgsql',
    'user'          => 'test',
    'password'      => 'test',
    'database'      => 'test',
    'host'          => 'localhost',
    'port'          => 5433,
    'driverOptions' => [\PDO::ATTR_CASE => \PDO::CASE_NATURAL],
];

The only way I could get a success (and it's totally wrong, I was just trying to see if I could get SOMETHING to work), was to add

$row['recordedOn'] = $row['recordedon'];

to DBALEventStore::deserializeEvent() just to keep the mismatch from happening.

Anyone know of the proper voodoo to use with the dbal connection to keep the column names as-is instead of getting lowercased?

Here is my use case:

    /**
     * @test
     */
    public function it_should_suspend()
    {
        $userId = UserId::generate();

        $this->scenario
            ->given([UserWasRegistered::with($userId, new Person)], $userId)
            ->when(SuspendUser::with($userId))
            ->then([
                UserWasSuspended::with($userId),
            ]);
    }

This is loosely related to #18 in that I ran into both of these problems more or less at the same time. Since my ID is an object I was going to have to do a lot of (string) $id in a lot of weird places and it was becoming unmanageable.

The issues were mainly around the fact that the InMemoryEventStore were using $id raw and assuming it was a stringish looking thing. I made changes to DBALEventStore to keep it consistent.

There should be a test to make sure this functionality continues to work but I wanted to make sure I'm on the right track here first. All of my domain models have an actual value object to represent their ID so this is going to be a big deal for me to have to change if I cannot pass the ID as-is in many places.

With this PR I tried to develop my idea up upcasting for the broadway library. It is based on a previous PR, but I have also provided an example of how to use this functionality via a test.

If the idea is approved, I would like to then work on the DBAL driver and symphony bundle for broadway.

How it works:

At the moment, the code works with the InMemoryEventStore class. In order to not touch the original class, I created a decorator for it. Regarding the DBAL driver integration, I could apply the decorator pattern or modify the original DBALEventStore class. What do you think?

The SequentialUpcasterChain class is a kind of registry used to register individual upcasters, which obviously need to be registered in an orderly manner.

I could potentially improve the SequentialUpcasterChain class by handling the upcasters' priority during instantiation in order to guarantee and enforce the ordering.

The example I have provided is based on the UserCreated event, which obviously is a bit of a stretch as it is conceptually an event that would be dispatched only once for each aggregate, but it should give the idea of how the feature works. A more realistic use case could be based on an event like PersonalDataRegistered, which could occur several times.