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
Synthetic Monitoring
Synthetic (active) monitoring where an application that mimics a user constantly checks the application for potential problems.
Related Patterns
- Try-Cancel/Confirm - To verify business activity can be achieved by initiating ‘business’ functionality the Try Cancel/Confirm pattern can be (ab)used. After executing the business functionality, the state changes can be reverted by cancelling the action.