Serverless priorities

What’s this issue all about?

Our hypothesis about serverless adoption is that

1. devs start to experiment with the technology on pet projects
2. they start to use the technology at their company, but outside of mission-critical tasks, mostly in backoffice scripts
3. as the technology proves its merits, the managers allow its use in production too

Our own survey sheds some light on this too: gitlab-org/uxr_insights#240 Basically, there are only a few mission critical use cases listed.

Still, we don't really know where users regularly are on this adoption path, as a result we don't know either how important different parts of a production-ready environment are.

See: https://docs.google.com/spreadsheets/d/1zSXrQZUJrz7XlIQieiGqQZR-ABoedwLJvI0jlqXZxnM/edit#gid=0

Who is the target user of the feature?

DevOps Engineers

What questions are you trying to answer?

What are the crucial ingredients of a viable serverless offering for backoffice scripts? What is the priority of different parts of a viable serverless offering for production scripts?

Core questions

Additional questions

What hypotheses and/or assumptions do you have?

What decisions will you make based on the research findings?

When do you need this research to be completed? (Milestone or date)

We would like to drive the product direction of 12.5 based on the outcome of this research. So, the deadline is around October 8.