<commit_before>## OpenFaaS backends

OpenFaaS is a framework for building serverless functions with containers and running them at scale.

We support two orchestration platforms or "backends":

* Docker Swarm
* Kubernetes

There is also community work in-progress to support:

* Rancher/Cattle

The Docker Swarm support is built-into the faas repo, but the Kubernetes support is provided by a microservice in the [faas-netes](https://github.com/alexellis/faas-netes) repo.

If you're thinking of writing a new back-end we'd love to hear about it and help you, so please get in touch with <EMAIL>. Existing implementations (like OpenFaaS) are written in Golang and this provides a level of consistency across the projects.

### I need a backend for X

This project is focusing on Docker Swarm and Kubernetes, but we're open to support from third parties and vendors for other backends:

Here are some ideas:

* Nomad
* Marathon Mesos
* AWS ECS
* Hyper.sh

If you would like to write your own back-end for `X` then you can write your own microservice that conforms to the [Swagger API](https://github.com/alexellis/faas/tree/master/api-docs) here.
<commit_msg>Update backends.md<commit_after>## OpenFaaS backends guide

OpenFaaS is a framework for building serverless functions with containers and running them at scale.

> Bring Serverless OpenFaaS functions to your favourite container platform.

We support two orchestration platforms or "backends":

* Docker Swarm
* Kubernetes

There is also community work in-progress to support:

* Rancher/Cattle

The Docker Swarm support is built-into the faas repo, but the Kubernetes support is provided by a microservice in the [faas-netes](https://github.com/alexellis/faas-netes) repo.

If you're thinking of writing a new back-end we'd love to hear about it and help you, so please get in touch with <EMAIL>. Existing implementations (like OpenFaaS) are written in Golang and this provides a level of consistency across the projects.

### I need a backend for X

This project is focusing on Docker Swarm and Kubernetes, but we're open to support from third parties and vendors for other backends:

Here are some ideas:

* Nomad
* Marathon Mesos
* AWS ECS
* Hyper.sh

If you would like to write your own back-end for `X` then you can write your own microservice that conforms to the [Swagger API](https://github.com/alexellis/faas/tree/master/api-docs) here.

{'fraction_non_alphanumeric': 0.05948419301164726, 'fraction_numerical': 0.0, 'mean_word_length': 4.4908675799086755, 'pattern_counts': {'":': 2, '<': 5, '<?xml version=': 0, '>': 6, 'https://': 4, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '3901358', 'n_tokens_mistral': 689, 'n_tokens_neox': 658, 'n_words': 339}