Skip to content
GitLab
Next
    • GitLab: the DevOps platform
    • Explore GitLab
    • Install GitLab
    • How GitLab compares
    • Get started
    • GitLab docs
    • GitLab Learn
  • Pricing
  • Talk to an expert
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    Projects Groups Topics Snippets
  • Register
  • Sign in
  • GitLab GitLab
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 52,764
    • Issues 52,764
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1,551
    • Merge requests 1,551
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
    • Test cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.orgGitLab.org
  • GitLabGitLab
  • Issues
  • #32543
Closed
Open
Issue created Sep 23, 2019 by Viktor Nagy (GitLab)@nagyv-gitlab🕊Developer

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 (closed), 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
Edited Sep 24, 2019 by Viktor Nagy (GitLab)
Assignee
Assign to
Time tracking