AgileDev
- Last Published: 2016-12-13
- |
- Version: 0.1.15-SNAPSHOT
- Guidelines
- Developers Setup
- Site Documentation
- Documentation
- Branching Models
- Javadoc guidelines
- Software Design Principles
-
Patterns
- API gateway
- Automated testing
- Builder
- Bulkheads
- Caching
- Circuit Breaker
- Client Side Discovery
- Command Query Responsibility Separation
- Deployment microservices
- Domain Driven Design
- Enterprise Integration Pattern
- Exception Handling
- Event Sourcing
- Microservice Architecture
- Monitoring
- Monolithic Architecture
- Scale Cube
- Self registration
- Server Side Discovery
- Service Connector
- Service Registry
- Service Statelessness
- Single Responsibility Principle
- System of Record
- Timeouts
- Try-Cancel/Confirm
- UUID
- 3rd party registration
- Glossary
- Abbreviations
- Modules
- Build Configuration
- AsciiDoctor output Doclet
- AsciiDoctor Site Diagram Activator
- Maven Site Indexer
- AgileDev common
- AgileDev parent POM
- JUnit BDD
- Design By Contracts for Java
- Cucumber Reporting
- Cucumber Reporting example
- Embedded MySQL Server
- Maven plugin Embedded MySQL Server
- CQRS for Spring
- Event Sourcing for Spring
- Try Cancel/Commit transactions for Spring
- Narayana Tomcat listener
- Tutorial ArchiMate
- Tutorial regarding CQRS and Event sourcing
- Tutorial Design by Contract
- Tutorial Domain Driven Design
- Tutorial Rest
- Project Documentation
- Project Information
Shared Kernel
Once separate teams are working on closely related bounded contexts they may produce systems that may not fit together.
Therefore agree with the teams to share some subset of the domain. Keep this kernel small. Within this kernel, include, beside the subset of the model, also the subset of code and/or the database design associated with that part of the model. This shared stuff has special status, and shouldn’t be changed without consulting the other team(s).