Notes from Implementing Domain Driven Design, chapter 2: Domains, Subdomains and Bounded Contexts (p58 and later only)
- User interface and service orientated endpoints are within the context boundary
- Domain concepts in the UI form the Smart UI Anti-Pattern
- A database schema is part of the context if it was created for it and not influenced from the outside
- Contexts should not be used to divide developer responsibilities; modules are a more suitable tactical approach
- A bounded context has one team that is responsible for it (while teams can be responsible for multiple bounded contexts)
- Access and identity is its own context and should not be visible at all in the domain of another context. The application services / use cases in the other context are responsible for interacting with the access and identity generic subdomain
- Context Maps are supposedly real cool