openfaas/faas

Research item: Long running batch-jobs / workflow

Open

#657 opened on Apr 18, 2018

View on GitHub
 (40 comments) (11 reactions) (0 assignees)Go (26,155 stars) (1,969 forks)batch import
design/reviewhelp wantedpriority/middlesize/xlskill/advanced

Description

Should we support long-running batch-jobs?

Are these in the scope of OpenFaaS functions which are typically several seconds in duration?

Are there primitives in Kubernetes such as jobs which we can leverage?

Kubernetes jobs example

Edit 29 Sept 2019

Since long-running jobs and workflows are related, I've added that to the title, so if you're looking for workflow, please feel free to comment with your use-case and whether it's for business purposes or for fun.

Contributor guide

Tech stack
godockerkubernetes
Domain
backendcloud
Issue type
research
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Basic knowledge of OpenFaaSUnderstanding of Kubernetes JobsFamiliarity with serverless concepts
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
This issue asks whether OpenFaaS should support long running batch jobs and workflows, and suggests using Kubernetes jobs as a primitive. To contribute, read the 40 existing comments to understand prior discussion and concerns. Then, research Kubernetes job API and how it could integrate with OpenFaaS. Propose a design or write a document summarizing pros/cons. Mention any maintainer feedback from comments.