More serverless designs

So far, we have seen three designs across three clouds and compared the serverless and non-serverless solutions. The architecture was specifically designed to demonstrate where serverless services fit it. In the real world though, it is not always like this. There is always a number of combinations of serverless and non-serverless services in the mix. The architecture could even be defined with parts of the design being replaced with different services that fulfill similar needs.

For example, in the non-serverless world, compute instances/virtual machines are often replaced by Kubernetes deployments – especially if the microservice running is of a stateless nature. Similarly, in event-driven architecture, a non-serverless design could incorporate Event Grid instead of managing its own Kafka cluster, which could be operation-intensive. Even in the case of serverless designs, it is not always beneficial to translate all your services to functions, especially...