The title of the article is "How a Monolith Architecture" but a good portion of the article describes considerations to take when moving services that seem not to be apart of the a monolith to a server-less cloud provider.

It seems that much of the advice centers around chopping up the monolith into services that can be run on a server-less cloud platform.

Uni-kernels, their promise of boot on demand and extremely small footprint, may help with a lot of this. In the very, very, near future devs will be able to package monoliths in ultra light-weight OS's that boot on demand and are optimized for the running application - and do all this on server-less cloud platforms without having to worry all that much.

I'd wager that in 2-3 years many of the use cases of containers will be replaced by Unikernel tech and the desire to run on serverless cloud platforms will be one very big use case.