| You can't do single server setup for your workloads if you are ISO 27001 compliant and, further, you must have a separate server for logging and monitoring. No matter load, there is a need for complexity for this certification. Not all employees log in daily. For a scheduling app, most people check a few times a week, but not every day. Daily active users (DAU) = around 10,000 to 20,000 Peak concurrency (users on at the exact same time) = generally between 1,500 to 2,000 at busy times (like when new schedules drop or at shift start/end times) Average concurrent users at any random time = maybe 50 to 150 Why cloud costs can add up even for us: Extensive use of real-time features and complex labour rules mean the app needs to handle a lot of data processing and ultimately sync into salary systems. An example: Being assigned to a shift has different implications for every user. It may trigger a nuisance bonus, and such a bonus could further only be triggered in certain cases, such as when you had the shifts assigned compared to when it start time. Lastly, there is the optimizing of a schedule why is computationally expensive. |
It would be interesting to read more about your policy on logging and monitoring and how you've implemented it.
Our app is a lot more demanding (I put 0.5 cores/user, 300 iops/user and 20Mb/s/user as requirements) and I forgot that there are also lighter use cases. We blew thru the thousands in free credits on aws in like 2 months and went immediately to Hetzner