mirror of
https://github.com/corda/corda.git
synced 2024-12-30 17:57:02 +00:00
Fixed typo; corrected note to 'certain databases'
This commit is contained in:
parent
895b745c37
commit
e817c95a78
@ -36,11 +36,11 @@ MN highlighted limitations in testability: Azure had confirmed support for geo r
|
|||||||
|
|
||||||
The design was noted to be dependent on a lot on external dependencies for replication, with R3's testing capability limited to Azure. Agent banks may want to use SAN across dark fiber sites, redundant switches etc. not available to R3.
|
The design was noted to be dependent on a lot on external dependencies for replication, with R3's testing capability limited to Azure. Agent banks may want to use SAN across dark fiber sites, redundant switches etc. not available to R3.
|
||||||
|
|
||||||
MN noted that databases are not yet officially supportedin Corda.
|
MN noted that certain databases are not yet officially supported in Corda.
|
||||||
|
|
||||||
### [Near-term-target](./near-term-target.md), [Medium-term target](./medium-term-target.md)
|
### [Near-term-target](./near-term-target.md), [Medium-term target](./medium-term-target.md)
|
||||||
|
|
||||||
Outlining the hot-cold design, MN Highlighted importance of ensuring only one node is active at one time. MN argued for having a tested hot-cold solution as a ‘backstop’. MN confirmed the work involved was to develop DB/SAN exclusion checkers and test appropriately.
|
Outlining the hot-cold design, MN highlighted importance of ensuring only one node is active at one time. MN argued for having a tested hot-cold solution as a ‘backstop’. MN confirmed the work involved was to develop DB/SAN exclusion checkers and test appropriately.
|
||||||
|
|
||||||
JC queried whether unknowns exist for hot-cold. MN described limitations of Azure file replication.
|
JC queried whether unknowns exist for hot-cold. MN described limitations of Azure file replication.
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user