Serverless
This item was not updated in last three versions of the Radar. Should it have appeared in one of the more recent editions, there is a good chance it remains pertinent. However, if the item dates back further, its relevance may have diminished and our current evaluation could vary. Regrettably, our capacity to consistently revisit items from past Radar editions is limited.
Adopt
We prefer a serverless architecture (over other architectures like microservices) for most new client solutions, depending on requirements, potential constraints as well available expertise, because of increased agility and time-to-market. A combination of a serverless and microservice architecture is also a viable option in many cases.
Serverless is often combined with an event-driven architecture.
We use the AWS definition of serverless:
"Serverless is the native architecture of the cloud that enables you to shift more of your operational responsibilities to AWS (..or a different cloud vendor..), increasing your agility and innovation. Serverless allows you to build and run applications and services without thinking about servers."