Space.domain.BoundedContext, implementing Space.Module

[rhyslbw]

I wrote in Trello, October 23rd 2015:

The thought here is that we can establish a more specific API for Bounded Context modules, just like we are doing with Application modules. This will mean the Space.Module becomes a lower level API, with lifecycle hooks being very flexible but not really intended to be used in implementations when using standard patterns and approaches.

Current thought is less drastic with treating Space.Module as a lower-level object, but still keen for (optional) opinionated modules where it makes sense… like here 😄

• Integrations - Space.domain.Integrations mapped as singletons Feature/Space.domain.Integration #10
• Application Mixin - requiredBoundedContexts mapped to requiredModules

Note from @DominikGuzei

Routers can already be auto-mapped in any module when the space:event-sourcing package is included in the app