separately. So instead of everything being loaded on a
single virtual machine, you break off the Apache web
server and PHP code from the MySQL database. By
themselves, they are much smaller in size and resource
utilization and can be scaled independently of each
other. Instead of having a gigabyte or more being taken
up for an operating system and hardware virtualization
of memory and other parts of virtualization, the
container simply shares the kernel of the underlying
operating system of the server it is running on. The
container is treated like an application and is run in an
isolated space within the operating system. Any binaries
and libraries needed to run the container are
prepackaged, which means you don’t have to touch the
container host server. Figure 13-12 shows a containerized
LAMP stack.
Figure 13-12 Containerized LAMP Stack
SERVERLESS
Serverless is one of the silliest names in the industry. Of
course, there is a server involved! However, this type of
application deployment mechanism is intended to make
it even easier to get an application up and running, and
the term serverless conveys this idea. You simply copy
and paste your code into a serverless instance, and the
infrastructure runs your code without any further
configuration. This type of deployment is also referred to
as function as a service, and it works best for applications
that run periodically or that are part of batch processes.