{"id":4269625,"date":"2021-09-16T08:53:36","date_gmt":"2021-09-16T06:53:36","guid":{"rendered":"https:\/\/www.deptagency.com\/insight\/when-containers-meet-serverless-a-match-made-in-heaven\/"},"modified":"2021-09-16T08:53:36","modified_gmt":"2021-09-16T08:53:36","slug":"when-containers-meet-serverless-a-match-made-in-heaven","status":"publish","type":"article","link":"https:\/\/www.deptagency.com\/en-au\/insight\/when-containers-meet-serverless-a-match-made-in-heaven\/","title":{"rendered":"When containers meet serverless: a match made in heaven"},"content":{"rendered":"
\n\t
\n\t

\n\t\t\tWhen containers meet serverless:
a match made
in heaven\t<\/h1>
\n\t<\/div>\t<\/div>\n\n\t
\n\n
\n\t
\n\t\t\n\t\t\t\t\t
\n\t\t\t\t\n
\n\t\tTraditionally, websites or applications are hosted on a virtual or physical server. And even though this seems to work out fine, it\u2019s hard to make the most out of your resources. However, so-called containers are designed to do the exact opposite: host applications and getting the most out of your resources. This brings along many advantages for both developers, engineers and businesses that need to adapt fast at any given moment. And when containers and serverless (also known as PaaS) meet, true magic happens.\t<\/h2><\/div><\/div>\n\n
\n\t\tThe basics of containers\t<\/h2><\/div><\/div>\n\n
\n\t\tMany developers have encountered the issue of code working perfectly fine on their machine, but when shipped into production to a local development environment, all of a sudden the code fails them. There are several reasons for that, think of differences in libraries, versions and operating systems. Local development with the use of containers is a great solution for these types of issues. But that\u2019s not all, the application it\u2019s used for runs quickly and reliably from one computing (cloud) environment to the other which makes it agnostic. They\u2019re lightweight and fast, and they include an entire environment: an application, all its dependencies, libraries and other binaries, and configuration files needed to run it, all together in one container.\t<\/p><\/div><\/div>\n\n
\n\t\tContainers and Serverless\t<\/h2><\/div><\/div>\n\n
\n\t\tAlthough container development isn\u2019t new per se, with Docker becoming increasingly popular, \u00a0it\u2019s a technology that brings along a lot of conveniences. Speed is one of them, as you can start and stop quickly with them and improve your resource utilisation because you can run many containers on a single machine. Moreover, it provides developers with the freedom to be in control of their work. Normally, a developer needs an engineer, but with this technology, he or she can work on the containers directly.

A big added value for containers comes to life when combining it with serverless hosting. This is a cloud-computing execution model in which the cloud provider runs the server infrastructure and manages the distribution of machine resources. The responsibility to manage and monitor servers and network components is a thing of the past since it\u2019s now under control by the cloud provider.
A preferred way of building up a serverless environment is by unrolling the infrastructure based on code. By doing this via a coding script it\u2019s easy to unroll multiple infrastructures with just a single-liner. Working like this provides yet another huge advantage for developers, namely that they can work in their own scripting mindset. So, by combining containers with serverless, developers become less dependent on ops who used to run this before and gain more control. And at this point is where the new rock stars enter the scene to make sure this actually takes flight: DevOps.

Working serverless, in turn, brings yet another set of advantages. It simplifies the process of deploying code into production, meaning fast development is a very likely possibility. Scaling up and down is easier, while\u00a0developers and operators do not need to spend time setting up and tuning complex autoscaling configurations or managing systems; the cloud provider is responsible for scaling the capacity to the demand and managing the underlying infrastructure.\u00a0Moreover, it can be more cost-effective, since there\u2019s no need to involve a hosting partner or host servers yourself which generally involves periods of underutilisation or idle time. Also, costs that usually go into licenses, installation, dependencies, support and maintenance are avoided when working serverless.
\t<\/p><\/div><\/div>\n\t\t\t<\/div>\n\t\t\t<\/div>\n\n\t\n\t