PaaS services, in comparison to IaaS, do not need the customer to manage and service the underlying infrastructure. The service is designed for scaling and high availability, by default. From a pricing perspective, a PaaS service is much cheaper than a dedicated IaaS service.

Looking at the design of PaaS services, you will find that a lot of them are already container-based but may not be multi-tenant at all. A PaaS solution can even be 1:1 for the relationship of the container and the customer.

Keep all of the points from the previous chapters. The real challenge to design a cloud- based and auto-scale solution is to figure out the service components you need and decide from which cloud vendor you would like to consume it. If the technical requirements for multi-cloud designs are set, you will just need to combine the services to best fit your requirements. In general, you should follow the the guidelines in the following order: first SaaS, then PaaS, and finally, IaaS.