In a scalable environment, you can't plan on 100% utilization. It takes time to provision a new server. A server that is at 100% utilization can't process additional incoming requests in a timely manner, which results in dropped or erroneous requests from the users' perspective. So the server in question must send a trigger well before it reaches 100% utilization so that no requests are dropped. Earlier in the chapter, I suggested a 60-80% target utilization before scaling. The exact number will highly depend on your specific choice software and hardware stack. Given your custom utilization target, we can calculate the number of users your infrastructure is expected to serve on average per instance. ...
Cost per user in a scalable environment
Get Angular 6 for Enterprise-Ready Web Applications now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
