dapr VS OpenFaaS

When you need more that synchronous 1:1 calls a communication middleware can be useful. When your services are running in Kubernets https://dapr.io/ is a good solution for m:n communication separation.

Even Microsoft itself chose Go for Dapr.

The OSS project I work on, Dapr (Distributed Application Runtime - an incubated CNCF project) implements the virtual actor pattern if anyone is interested.

https://docs.dapr.io/developing-applications/building-blocks...

https://github.com/dapr/dapr

There's an emerging piece of open source tech I'm very excited about. If you haven't heard of Dapr, it's one of the newest additions to the Cloud Native Compute Foundation (CNCF) and promises to provide portable and reliable microservices. While on the surface that may sound great, a lot of you may be wondering "ok but what is it? how does it work?" While analogies and comparisons will never be perfect, I love to use them to help me contextualize. So while the comparison is imperfect, I personally think of Dapr like jQuery for microservices.

Dapr is a Cloud Native Computing Foundation project currently at the Incubating stage. It was created to help us as developers build microservices quickly with ease.

I'm trying to find a solution to integrate various microservices and stumbled upon Dapr, which looks pretty interesting.

Azure Container Apps is a container orchestration platform for deploying modern applications and microservices. With Azure Container Apps you can deploy your containerized apps without the need to take on the overhead of managing the infrastructure of the underlying systems. This service is still in preview, but provides you with the ability to use your preferred language or framework to build microservices with support for Distributed Application Runtime (Dapr). There's also scaling of your containers with Kubernetes Event-Driven Autoscaling (KEDA).

I think this might be what youre looking for. https://www.openfaas.com/

> I’m of the opinion that lambda-as-in-serverless is an evil.

Are there any other serverless solutions that you'd recommend?

Maybe a more open cloud function solution that could also be self-hosted, should the need arise?

As far as I know, OpenFaaS might serve that niche for some, though of course there will be no cloud solutions as large as Lambda available: https://github.com/openfaas/faas

Also there used to be IronFunctions, but those seem basically abandoned at this point: https://github.com/iron-io/functions

Main page (check out the function examples at the bottom - even bash is covered!): https://www.openfaas.com/

OpenFaaS

openfaas is fairly popular

Learning Kubernetes (K8s) for me was about getting pissed off enough at Bezos for all the money he was making off of me lol. I wanted to have my own little infrastructure that I control but without having to babysit it. I tried Docker Swarm, which was nice but wasn’t translating into professional-grade cluster experience. I found a project called Open FAAS that let me deploy my own Lambda/serverless. It ran on K8s. So, I followed a few tutorials on K3s (a lightweight version of K8s for the pi) and deployed it with K3sup. The OpenFAAS project, K8s, and Docker are written in Golang, so I learned some of that with A Tour Of Go. After branching out into the K8s world for a bit, I decided to get my Certified Kubernetes Application Developer (CKAD). I took this Udemy course and passed the test on the first go. You’ll learn just about everything you’ll need to know about K8s from that experience.

The call for MIT / Apache 2.0 licensing at the end of the post was surprising, given the issues that the author outlined.

Grafana and Minio have both moved to AGPL / dual licensing from permissive licenses to stimulate licensing sales and revenue. As the maintainer of OpenFaaS, it's been a struggle to correct the balance of corporations freeloading [0] vs. contributing code or finances.

GitHub Sponsors has also given very mixed results [1]

In the same week we saw the maintainer of a popular OSS work almost throw in the towel [2]

After 5 years, we're starting to see customer interest only by holding new features and enhancements back i.e. Open Core. There are still problems with this approach, and paying customers end up funding all the R&D required for the free users - amongst other things like competition from hobbyist users who covet features that are more appropriate in production than on your Raspberry Pi cluster.

[0] https://github.com/openfaas/faas/blob/master/ADOPTERS.md