Skip to content

Latest commit

 

History

History
49 lines (32 loc) · 3.92 KB

README.md

File metadata and controls

49 lines (32 loc) · 3.92 KB
Raw

predaddy

Latest Stable Version Scrutinizer Code Quality SensioLabsInsight Gitter chat MIT license Flattr this

master 1.2 2.2 3.0
Build Status Build Status Build Status Build Status
Coverage Status Coverage Status Coverage Status Coverage Status

It is a library which gives you some usable classes to be able to use common DDD patterns. Some predaddy components can be used in any projects regardless of the fact that you are using DDD or not. I have got several ideas from Google's Guava EventBus and Axon framework.

Some libraries are used which are just API libraries and you must care for their implementations:

  1. lf4php for logging. Without an implementation predaddy is not logging.
  2. trf4php for transaction management. In most cases you will need to use a trf4php implementation (eg. trf4php-doctrine)

Components

For more details see the components (click on the titles):

  1. Message handling

    It's an annotation based publish/subscribe implementation, can be used any projects even without DDD/CQRS/Event Sourcing.

  2. CQRS and Event Sourcing

    Complex solution for handling aggregates, based on the message handling component.

  3. Presentation - finders, etc.

    Common classes and interfaces for handling the read side. It also can be used in any applications.

  4. Testing - helper for aggregate testing

    Fixtures to ease aggregate testing.

Examples

You can find some small CLI examples in the sample directory.

A sample project is also available which shows how predaddy should be configured and used: https://github.com/szjani/predaddy-issuetracker-sample