diff --git a/docs/dg/dev/best-practices/non-functional-requirement-templates/operational-and-deployment-guidelines.md b/docs/dg/dev/best-practices/non-functional-requirement-templates/operational-and-deployment-guidelines.md
index c93ab7ddaf..a95c4ddc18 100644
--- a/docs/dg/dev/best-practices/non-functional-requirement-templates/operational-and-deployment-guidelines.md
+++ b/docs/dg/dev/best-practices/non-functional-requirement-templates/operational-and-deployment-guidelines.md
@@ -66,3 +66,7 @@ The rollback scripts must not break the behavior of the current system:
 * Glue GET requests with subsequent Zed requests should be under 180ms on average.
 * Glue GET requests without subsequent Zed requests should be under 140ms on average.
 * Glue POST, PATCH, and PUT requests with subsequent Zed requests should be under 290ms on average.
+
+## Scaleability guidelines
+
+[P&S](docs/dg/dev/backend-development/data-manipulation/data-publishing/publish-and-synchronization.html) processes must have O(n) time complexity and O(n) resource complexity. In other words, they scale linearly with the number of entities they're processing. Specifically, memory and CPU consumption must grow proportionally to the number of entities. For example, if a process handles 100 entities, its resource consumption is X. When it handles 200 entities, the resource consumption must not exceed 2X.