You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: _posts/2020-04-17-introducing-faasd.md
+9-7Lines changed: 9 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,7 +23,7 @@ From the first iteration of OpenFaaS in 2016 (then called "faas"), portability a
23
23
24
24
The [faas-provider](https://github.com/openfaas/faas-provider) SDK allowed us to do this and was extracted from the core project shortly after adding support for Kubernetes. We've had a number of other community providers, but this is the one with the most traction today.
25
25
26
-
> It's my belief that Kubernetes is the best way to run OpenFaaS in production for everything from edge deployments to large scale platforms.
26
+
> It's my current opinion that Kubernetes is the best way to run OpenFaaS in production for everything from the edge to the very largest deployments.
27
27
28
28
After several years of working with Kubernetes and similar technology, I've become numb to its complexities and that makes me a bad judge of whether it's easy to use or not. OpenFaaS aims to abstract away the repetitive nature of YAML files and to add value through its API and ecosystem.
29
29
@@ -123,17 +123,19 @@ There's multiple ways to deploy faasd, pick whichever suits your needs. The core
123
123
124
124
## Wrapping up
125
125
126
-
OpenFaaS is best run on Kubernetes, but this does come with a learning curve and for some teams, an ongoing maintenance cost. faasd presents a new option for teams that want to start out with Serverless and keep it both open-source and portable too.
127
-
128
-
We hope that faasd could provide a way for us to deprecate support for Docker Swarm, which is currently made available via [faas-swarm](https://github.com/openfaas/faas-swarm).
129
-
130
-
> If you're using OpenFaaS with Swarm in production, I'd strongly suggest that you get in touch to discuss your requirements: [support@openfaas.com](mailto:support@openfaas.com).
126
+
OpenFaaS is best run on Kubernetes, but this does come with a learning curve and for some teams, an ongoing maintenance cost. Whilst Kubernetes is great for scaling up and scaling out, scaling down can be just as important, and that's where faasd comes into its own. faasd presents a new option for teams that want to start out with Serverless and keep it both open-source and portable too.
131
127
132
128
* For production use and scale-out - use OpenFaaS on Kubernetes or k3s
133
129
* For local development and edge/Raspberry Pi - use OpenFaaS on k3s or Kubernetes
134
130
* Small teams / no-clustering: use faasd
135
131
136
-
Read more on the [deployment page](https://docs.openfaas.com/deployment/)
132
+
Read more on the [OpenFaaS deployment page](https://docs.openfaas.com/deployment/)
133
+
134
+
Are you still using Docker Swarm in production?
135
+
136
+
We hope that faasd could provide a way for us to deprecate support for Docker Swarm, which is currently made available via [faas-swarm](https://github.com/openfaas/faas-swarm).
137
+
138
+
> If you're using OpenFaaS with Swarm in production, I'd strongly suggest that you get in touch to discuss your requirements: [support@openfaas.com](mailto:support@openfaas.com).
0 commit comments