ExternalVendorCode/corda
1
0
Fork 0
mirror of https://github.com/corda/corda.git synced 2025-01-16 17:59:46 +00:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity

Added goals/non-goals headers; fixed typo

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

6
docs/source/design/hadr/design.md
View File

@ -69,13 +69,13 @@ Artemis, H2 database, Flow State Machine, P2P bridging. All storage is on the lo
- The backup strategy is unclear. - The backup strategy is unclear.
## Requirements ## Requirements
### Goals
* A logical Corda node should continue to function in the event of an individual component failure or (e.g.) restart. * A logical Corda node should continue to function in the event of an individual component failure or (e.g.) restart.
* No loss, corruption or duplication of data on the ledger due to component outages * No loss, corruption or duplication of data on the ledger due to component outages
* Ensure continuity of flows throughout any disruption * Ensure continuity of flows throughout any disruption
* Support software upgrades in a live network * Support software upgrades in a live network
* Non-goals (out of scope for this design document)
### Goals (out of scope for this design document)
* Be able to distribute a node over more than two datacenters. * Be able to distribute a node over more than two datacenters.
* Be able to distribute a node between datacenters that are very far apart latency-wise (unless you don't care about performance). * Be able to distribute a node between datacenters that are very far apart latency-wise (unless you don't care about performance).
* Be able to tolerate arbitrary byzantine failures within a node cluster. * Be able to tolerate arbitrary byzantine failures within a node cluster.
@ -162,7 +162,7 @@ Cleaner handling of disconnects from the external components (Artemis and the da
- Faster failover as no manual intervention. - Faster failover as no manual intervention.
- We can use Artemis replication protocol to replicate the message store. - We can use Artemis replication protocol to replicate the message store.
- The approach in integrated with preliminary steps for the float. - The approach is integrated with preliminary steps for the float.
- Able to handle loss of network connectivity to the database from one node. - Able to handle loss of network connectivity to the database from one node.
- Extraction of Artemis server allows a more standard Artemis deployment. - Extraction of Artemis server allows a more standard Artemis deployment.
- Provides protection against resource leakage in Artemis or Node from affecting the other component. - Provides protection against resource leakage in Artemis or Node from affecting the other component.