Comparing siteless UIs and serverless
After microservices had been established on the backend, a new kind of architecture was introduced that became popular: serverless or FaaS architecture. In a nutshell, this architecture reduced backend services to single functions where all the essentials had been handled by an integrated runtime.
In the beginning, serverless was mainly a selling point for cloud providers. They advocated the new pattern with fewer dedicated costs. After all, since these functions use a shared and provided runtime, they are not required to run in custom containers that need dedicated resources. Instead, they can just sit idle and wait for a request, being invoked only when required. The runtime would be able to serve many different functions from many different tenants.
In the following sections, we’ll focus our comparison on two major aspects: how local development works and how modules are published. We’ll start with the setup for local development...
