Mention in design doc solution template that effects on replication should be considered
Some designs may work well for a single master but then generate
unexpected overhead during replication, hence we should consider this
aspect early.
Signed-off-by: Edwin Kempin <ekempin@google.com>
Change-Id: Iee162a5d39359ee5b8056a4d7137aaae19b6f8ee
diff --git a/Documentation/dev-design-doc-solution-template.md b/Documentation/dev-design-doc-solution-template.md
index 66b8ae7..622c840 100644
--- a/Documentation/dev-design-doc-solution-template.md
+++ b/Documentation/dev-design-doc-solution-template.md
@@ -20,8 +20,13 @@
### <a id="scalability"> Scalability
-How does the solution scale? Consider both, data size increase (if
-applicable) and traffic increase (if applicable).
+How does the solution scale?
+
+If applicable, consider:
+
+* data size increase
+* traffic increase
+* effects on replication across sites (master-slave and master-master)
## <a id="alternatives-considered"> Alternatives Considered
