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
Side effect free functions.
Interactions of multiple rules or compositions of calculations become extremely difficult to predict. The developer calling an operation must understand its implementation and the implementation of all its delegations in order to anticipate the result. The usefulness of any abstraction of interfaces is limited if the developers are forced to pierce the veil.
Therefore, place as much as possible of the program into functions/operations that return results with no observable side effects. Strictly segregate method which result in modifications to observable state into very simple operations that do not return domain information. Further control side effects by moving complex logic into Value Objects when a concept fitting the responsibility present itself.