wg-serverless
specification
Our great sponsors
wg-serverless | specification | |
---|---|---|
7 | 5 | |
1,504 | 682 | |
0.0% | 2.5% | |
0.0 | 7.4 | |
about 1 year ago | 9 days ago | |
TypeScript | ||
Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
wg-serverless
-
Personal programming projects to improve my chances at a job (I have a homeserver)
Check out CNCF Projects. Contributing to some of these open source projects is a great way to gain skills and land a job.
-
The quickest way to add an integration test to your kubernetes environment
would indicate if your cluster could retrieve content from cncf.io or if cncf.io is up.
-
Stateless, Secretless Multi-cluster Monitoring in Azure Kubernetes Service with Thanos, Prometheus and Azure Managed Grafana
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.
-
DigitalOcean Functions: A powerful serverless computing solution
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.
-
Serverless 101
github.com/cncf/wg-serverless/blob/master/w..
-
Getting Started with CloudEvents and AsyncAPI
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.
specification
- FLaNK Stack Weekly 27 March 2023
-
No-code or Workflow as code? Better both
Once you have defined the workflow on a diagram, a JSON, following the Serverless workflow specification, is stored in KuFlow. With this specification, we can use all the great tools/libs that are developed.
-
Temporal - the iPhone of System Design
This example happens to be from Google, but you can compare similar config-driven syntaxes from Argo, Amazon, and Airflow. The bottom line is you ultimately find yourself hand-writing the Abstract Syntax Tree of something you can read much better in code anyway:
What are some alternatives?
spec - CloudEvents Specification
asyncapi-to-postman - Creates a Postman collection from an AsyncAPI file.
generator - Use your AsyncAPI definition to generate literally anything. Markdown documentation, Node.js code, HTML documentation, anything!
ingress-nginx - Ingress-NGINX Controller for Kubernetes
dotnet-nats-template - .NET template for NATS
AKS - Azure Kubernetes Service
k8s-event-grid-bridge - A simple event bridge for Kubernetes native events to Azure Event Grid.
gateway - Manages Envoy Proxy as a Standalone or Kubernetes-based Application Gateway
smi-spec - Service Mesh Interface
eu-dcc-hcert-spec - Electronic Health Certificates Specification
aquarium - AI-controlled Linux Containers
prometheus - The Prometheus monitoring system and time series database.