Serverless Vision: primary user
Our focus persona might change as the ~"group::serverless" matures, but there is always a user whom we focus. Behind each feature developed there are intended users.
Initial persona
According to my current understanding, our primary user is best described as
A technology enthusiast experimenting with Kubernetes and serverless.
This means, that we want to make it really easy to get started with serverless from zero, and we focus less on running and managing serverless. As we are speaking about a technology enthousiast, we don't have to focus on widely used serverless providers, like AWS, but we can focus on the cutting-edge, like Knative.
Missing features
I think most of the necessary features are either available or are collected under &1726, I only list the ones I currently find missing:
- project template for serverless
Critique
This is definitely not a persona we can build upon. As enthousiasm dies, the user would leave.
Persona v1.0
a developer who wants to automate something and Get The Work Done, not necessarily carrying about servers/containers/kubernetes
At this stage we should differentiate between a few directions. The primary persona is clearly the developer, but we have to consider a secondary persona too:
an operations engineer who wants to give devs freedom while still keeping security under control and having a thorough overview of all their systems
In this situation, our team already has a running infrastructure and we should integrate with that infrastructure.
To k8s or not to k8s - that is the question
We have two distinct user groups
- Those who use serverless with serverless service providers (Lambda, GCC, Zeit, etc)
- Those who use serverless inside their K8s cluster
The latter group are the enterprise users. The former are usually SMBs.
Missing features
- forward serverless logs to central log storage
- deploy only related / changed functions