*From a business POV. * *My Free Business Advice Has Double Money Back Warranty!** 🤪*
Even very small businesses should make *scale friendly* decisions. Always position towards account growth rather than using constraints when possible. Have a response plan BEFORE it happens. In the use case mentioned: *Hard* metal self hosted, increase memory, its a cheap, one time expense. Writing constraints often has unintended consequences elsewhere . . . and actually costs more than the memory. A simple business promotion can increase accounts rapidly and then customers and employees are left waiting while the server juggles insufficient memory. *Cloud*, maybe use a constraint until the volume increases to a defined plateau where the cost of upscaling memory as a recurring cost is justified. Maintain awareness of Tech Debt and have a simple mitigation plan to constantly think towards growth. If allowing growth without restraint or interruption *= *the ability to scale, THEN constraints which artificially lower performance are contra to those goals. Never intentionally degrade your capacity UNLESS its an absolute MUST. -- Paul
