ExternalVendorCode/corda
1
0
Fork 0
mirror of https://github.com/corda/corda.git synced 2025-03-28 22:59:09 +00:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity

Added missing spaces

Browse Source
This commit is contained in:
David Lee 2018-01-15 18:47:17 +00:00 committed by GitHub
parent d390716a9b
commit 895b745c37
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
docs/source/design/hadr/decisions/near-term-target.md
View File

@ -27,15 +27,15 @@ Designing for high availability is a complex task which can only be delivered ov
#### Advantages
1. Flushes out lots of basic deployment issues that will be ofbenefit later.
1. Flushes out lots of basic deployment issues that will be of benefit later.
2. If stuff slips we at least have a backstop position with hot-cold.
3. For now, the only DR story we have is essentially a continuationof this mode
3. For now, the only DR story we have is essentially a continuation of this mode
4. The intent of decisions such as using a loadbalancer is to minimise code changes
#### Disadvantages
1. Distracts from the work for more complete forms of HA.
2. Involves creating a few components that are notmuch use later, for instance the mutual exclusion lock.
2. Involves creating a few components that are not much use later, for instance the mutual exclusion lock.
## Recommendation and justification
@ -43,4 +43,4 @@ Proceed with Option 2: Hot-cold.
## Decision taken
**[DRB meeting, 16/11/2017:](./drb-meeting-20171116.md)** Adopt option 2: Near-term target: Hot Cold (RGB, JC, MH agreed)
**[DRB meeting, 16/11/2017:](./drb-meeting-20171116.md)** Adopt option 2: Near-term target: Hot Cold (RGB, JC, MH agreed)