wg-serverless VS OpenWhisk

Check out CNCF Projects. Contributing to some of these open source projects is a great way to gain skills and land a job.

would indicate if your cluster could retrieve content from cncf.io or if cncf.io is up.

This solution builds upon well-established Cloud Native Computing Foundation (CNCF) open source projects like Thanos and Prometheus,together with a new managed services, Azure Managed Grafana, recently released in public preview. It allows for ephemeral clusters to still have updated metrics without the 2-hours local storage of metrics in the classic deployment of Thanos sidecar to Prometheus.

Not ELI5 but see https://github.com/cncf/wg-serverless/tree/master/whitepaper...

Some people go monolithic app but best practice is usually one function per route.

Traditional servers come with management overhead (e.g. defining/managing/monitoring scaling) and by using Serverless servers you avoid that overhead and optimize for good engineers which are almost always your bigger cost center.

github.com/cncf/wg-serverless/blob/master/w..

As stated in a white paper by the CNCF serverless working group, there are two primary serverless personas:

The CloudEvents specification is under the CNCF Serverless working group since 2018. The spec's purpose is describing event data in a common way. This is useful in many scenarios, for example, routing events to the appropriate subscribers depending on the type of the event. Since applications can use a lot of different transports to send and receive events, the CloudEvents spec is protocol-agnostic so it defines protocol bindings in order for the metadata to be correctly mapped for HTTP, AMQP, Kafka, etc.

Serverless functions are now offered by many cloud providers, as well as having options like OpenFaaS, Knative, Apache's Openwhisk and more from the open source community that run in environments ranging from one server all the way up to globally replicated private clusters.

OpenWhisk - https://openwhisk.apache.org

The serverless functions with Digital Ocean are based on Apache Open Whisk, so the service has additional name space, which need to go into the URL.

The two biggest options are OpenWhisk and OpenFaas. Check out /r/serverless for more options. I'm experimenting currently with OpenFaas as it's the lighter weigh to of the two.

If you meant lambda for cloud functions provided by Amazon then this is open source and free, as long as you host it yourself: https://openwhisk.apache.org/

There are so many of them in big data, e.g. Kafka, Spark, Flink, Delta, Snowplow, Finagle, Deequ, CMAK, OpenWhisk, Snowflake, TheHive, TVM-VTA, etc.

The foundation is Apache OpenWhisk https://github.com/apache/openwhisk with DO specific customization to work with managed databased, log shipping, and other DO specific capabilities. The closest programming model is AWS Lambda in terms of the semantics and execution model.