Modernize Blueprint
von Peter Verster
1. No Duplication of Data
1.1. why is duplicating data not good ?
1.2. what are the benefits of duplicating it
1.3. what are the implications of changing
1.4. what is the approach
1.4.1. APIs
1.4.2. Domain Entities
1.4.3. Domain Events
1.4.4. in-memory
1.4.5. principles
2. Business Critical SLAs
2.1. Global EOD
2.2. Intraday
2.3. system availability
2.4. performance
3. Degrade gracefully
3.1. reduced functionality
3.1.1. decomposition
3.2. fault tolerance
3.2.1. fault management
3.2.1.1. MTTR
3.2.1.2. MTTD
3.2.2. hardware fault tolerance
3.2.3. software fault tolerance
3.2.4. transient fault tolerance
3.3. single point of failure
3.3.1. shared nothing
3.3.1.1. data
3.3.1.1.1. sharding
3.3.1.1.2. partitioning
3.3.2. sharding
3.3.3. dependency
4. Risk Reduction
4.1. reduce the likelihood
4.2. reduce the impact
4.3. types
4.3.1. system availability (uptime)
4.3.2. errors
4.3.3. meeting SLAs
4.3.4. time to market
4.3.5. responsiveness / performance