summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBrian Grant <bgrant0607@users.noreply.github.com>2017-02-20 08:42:08 -0800
committerGitHub <noreply@github.com>2017-02-20 08:42:08 -0800
commitaba91e6e94936bb29c17909cf8237e3d0aec177f (patch)
treec3578d54eab106cbb9c72cdcd25d9dfa569e9e10
parentaf2e0676437438e3ca43f8e04e0d78b33fce8d68 (diff)
Update principles.md
-rw-r--r--contributors/design-proposals/principles.md1
1 files changed, 1 insertions, 0 deletions
diff --git a/contributors/design-proposals/principles.md b/contributors/design-proposals/principles.md
index 4e0b663c..fe66d519 100644
--- a/contributors/design-proposals/principles.md
+++ b/contributors/design-proposals/principles.md
@@ -30,6 +30,7 @@ implementation-oriented (think control knobs).
given the desired state and the current/observed state, regardless of how many
intermediate state updates may have been missed. Edge-triggered behavior must be
just an optimization.
+ * There should be a CAP-like theorem regarding the tradeoffs between driving control loops via polling or events about simultaneously achieving high performance, reliability, and simplicity -- pick any 2.
* Assume an open world: continually verify assumptions and gracefully adapt to
external events and/or actors. Example: we allow users to kill pods under
control of a replication controller; it just replaces them.