ziobrando / d3n Goto Github PK

I have Spring-style dependency injection in mind, butblooksmlike this is not the dominant idiom in ruby world. Let's find a cleaner way to wire up things.

A little advanced, maybe. But that's where I want to go.

So far, I've simply wired up Sequel and made it work. Implicitly it assumes auto-commit and does the job in the repository. This is not the behavior I am looking for.

It will probably be strictly required in case of polyglot persistence, but in general I need a way not to have repositories dependent on the chosen persistence framework.

Aggregates should talk each other using Domain Events. I am looking for a publish-subscribe communication mechanism. In real world it has to be synchronous, but for modeling purpose only a quick synchronous bus would still provide some interesting insights.

So far the implementation is rather messy. No clear choice between a facade and a command.

I started with that, but dropped it. Let's make it work again in a clean and elegant fashion.

There are 3 places where data is setup. This has to become only one place. Probably the Rake Task.

So far I created a Configuration class. No Singleton or other frills. Just hardcoded configuration.
It works, but I am definitely looking for something cleaner.

Suggestions welcome :-)

Some tests are data dependent.
Perform cleanup after tests and ensure that the (few) test that need populated data are consistent.