With Scalalability and Availability I mean the capability to continue working even though software, hardware or human faults occur even though the load is suddenly increasing.
Coming from a pure IT / Kubernetes / Netflix perspective, one would require clustering, load balancing, etc., so that if one instance fails, gets updated, etc., immediately another takes over.
HighByte has that to some degree "primary/secondary failover" or "manual clustering requiring multiple installation". However, this will result in downtime and effort when trying to scale it up.
You could now ask whether you actually need these requirements and this is something that we cannot decide for companies 🙂