It's not though, few server usecases allow/require your environment to change every day.
OpenSUSE Tumbleweed is a lot more stable than ArchLinux for that kind of stuff though. It stages updates in tested snapshots. ArchLinux updates just error if you time them right.
Anecdotal, but I never had an Arch install fail after updating (maybe the one time my EFI partition was full, but not specific to Arch). While I have a laptop running OpenSUSE Tumbleweed that failed to start after the third update I did on it.
> While I have a laptop running OpenSUSE Tumbleweed that failed to start after the third update
Very possible, Tumbleweed has had some embarrassing failures.
But when it comes to rolling release on servers I'd still prefer OpenSUSE.
OpenSUSE has whole distributions (MicroOS & Aeon) dedicated to performing automatic updates. ArchLinux is not really made with automatic updates in mind.
Big part of that is possible because OpenSUSE releases Tumbleweed in "snapshots". This means that updated packages are basically staged and tested together before release. This happens a few times a week. If you then experience a failure you can always use an older tumbleweed snapshot. In theory that should provide more stability, but there has recently been a lot of instability especially with SELinux being enabled by default.
