wg-serverless
asyncapi-to-postman
wg-serverless | asyncapi-to-postman | |
---|---|---|
7 | 1 | |
1,503 | 2 | |
-0.1% | - | |
2.3 | 0.0 | |
3 months ago | over 2 years ago | |
JavaScript | ||
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..
-
Running Serverless Applications on Kubernetes with Knative
As stated in a white paper by the CNCF serverless working group, there are two primary serverless personas:
-
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.
asyncapi-to-postman
-
Getting Started with CloudEvents and AsyncAPI
There is already quite a few tools and the tooling ecosystem is increasing! I've recently seen a repository that enables the creation of Postman collections from an AsyncAPI spec. I've also seen architecture documents being generated from multiple AsyncAPI specs too, having a tool that can understand relations between applications and then output a diagram is pretty cool.
What are some alternatives?
dotnet-nats-template - .NET template for NATS
generator - Use your AsyncAPI definition to generate literally anything. Markdown documentation, Node.js code, HTML documentation, anything!
spec - CloudEvents Specification
AKS - Azure Kubernetes Service
cupid - A library that focuses on finding and analyzing the relationships between AsyncAPI documents. It outputs a map of the system architecture. Except for a default map, it is possible to get output as mermaid.js flow diagram, PlantUML class diagram and more to come.
k8s-event-grid-bridge - A simple event bridge for Kubernetes native events to Azure Event Grid.
ingress-nginx - Ingress-NGINX Controller for Kubernetes
specification - Serverless Workflow Specification
nodejs-ws-template - Node.js WebSockets template for the AsyncAPI Generator. It showcases how from a single AsyncAPI document you can generate a server and a client at the same time.