> Except it bills itself as serverless. In a PaaS your apps need to have a server (e.g., http server). Serverless (e.g., FaaS or Brigade) elsewhere doesn't need

> Except it bills itself as serverless. In a PaaS your apps need to have a server (e.g., http server). Serverless (e.g., FaaS or Brigade) elsewhere doesn't need this. Stuff isn't long running. I think this comes down to the difficulties of terminology. I think of FaaS as a PaaS with some extra features (scale-to-zero being the most-noticeable). "Serverless" is a catch-all term for a variety of workloads, of which FaaS is the most visible. > Pipelines? That doesn't appear to be in the docs. What is Pipelines? It's a proposal[0] to evolve Concourse into being a Knative component, picking up from Build for complex workflows. I've been working on parts of this with various folks over the past few months. I should emphasise that it is a proposal. For what you do with Knative today, use Build. It's a simple abstraction and it works right now. [0] https://docs.google.com/document/d/1PicF7UhvSBpZLwichuY5hdhTX7Sl6aak2OzwDK8G78s/edit https://docs.google.com/document/d/1PicF7UhvSBpZLwichuY5hdhT... (to view, join the knative-dev group: https://groups.google.com/forum/#!forum/knative-dev https://groups.google.com/forum/#!forum/knative-dev)