3 ms·
"Immutable Server" seems like an oxymoron. Frequent refreshes are great, but your system is only doing something useful once it has "mutated" (i.e. accepted ex
by _bpo 13y ago
"Immutable Server" seems like an oxymoron.
Frequent refreshes are great, but your system is only doing something useful once it has "mutated" (i.e. accepted external data to operate on).
The tradeoff system designers have to make is frequency of refreshes vs the cost of transferring interesting data to that server.
Seems like your organization has just coined a new synonym for "gold master"
- regularfry 13y agoYou can do it the other way round: have your data on direct-attached storage and network mount the root filesystem.
- contingencies 13y agoWe do well with DRBD as an alternative here .. adequate network redundancy without performance penalties.
- regularfry 13y ago"Adequate" is an interesting word :-) We don't consider DRBD in anything other than synchronous replication mode to be reliable, which puts a fair performance penalty on it.