As fair warning, I just signed up so I'm still picking apart enhance and learning.
Ned Slightly unrelated but on the wprocket/image optimization point - You can use the LSCache plugin on any system, Even if it's on NGINX it just won't take full advantage of the lsphp/server level cache when combined with LiteSpeed, You can have NGINX just do that automatically though.
True, but the Nginx cache comes in two flavours, fastcgi/redis for full-page cache of which both are limited in how you can store and manage the cache. Litespeed however, is more advanced in this regard allowing for more flexibility and options. For instance, you can exclude page sections from being cached. The LSCache plugin can be used with Nginx, but the more advanced caching and cache control wouldn't be available. There is someone I know trying to clone the same functionality into Nginx as a module that would work with LSCache plugin. So hands down Litespeed + LSCache has the most advanced caching system and helper plugin available for WordPress at this time. However, Nginx fastcgi cache is blazing fast and great for static sites that don't require a login or continuos updates.
Ned I do see the value in LiteSpeed, but on a more monolithic scale or on a dedicated machine where I'm looking for max density, With enhance you'd be paying $26-46/Mo for each server, When you can have something just as if not more performant on NGINX + FastCGI Cache and WordPress plugins like W3 Total Cache/ WP Fastest Cache & EWWW/reSmush.it.
Depending on how you do your infrastructure. You could use bare metal directly or virtualize bare metal and license each instance. Have some instances as Nginx and others for Litespeed that are Woo/LMS/BB. Full bare metal is hard to manage, virtualization helps. Caching is great with Nginx, but once you log in or checkout there's no more cache. That's where LSCache kicks in and can provide some small amounts of caching, including proper cache eviction and bypass using the plugin versus nginx config.
Ned PHP X-Ray / AccelerateWP / HardenedPHP are all good options for those willing to pay but runs into the same per server licensing issue too.
PHP X-Ray is an APM, of which there are many options out there and it would be good to add support for a handful of APMs so there's a choice. As for AccelerateWP, pretty sure this can be built into the enhance stack without shelling out money to Cloudlinux. HardenedPHP, there's other companies out there that provide a similar service, add support to use these in the stack. But a bigger issue is why are we not pushing for the adoption of PHP 8.1? We'll have the same issue again and again if there isn't a consistent effort to stay ahead of PHP releases not only in the WordPress core but also for all plugin developers. But I understand that sometimes there are situations where a plugin was custom developed or discontinued and can't be moved to PHP 8.1, but that also means it's not being active maintained and could have other issues such as performance and security.
Mason Kernelcare (no reboots)
There's more than one live patching no reboot kernel update vendors, support them all and leave it up to choice. Otherwise kexec or wait. Most reboots I've seen now are 15 seconds in virtual instances.
