podtato-head
litmus
Our great sponsors
| podtato-head | litmus | |
|---|---|---|
| 5 | 1 | |
| 340 | 155 | |
| 0.3% | 2.6% | |
| 1.3 | 0.0 | |
| about 2 months ago | over 2 years ago | |
| Shell | Rust | |
| Apache License 2.0 | MIT License |
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.
podtato-head
-
any good repo to do some projects?
You should checkout Podtato Head from the CNCF. It has a bunch of different deployment scenarios. https://github.com/podtato-head/podtato-head
-
Recommended tutorial on setting up a generic web app so i can better understand cicd and app lifecycle
https://github.com/podtato-head/podtato-head has great examples of deploying an app using different methods.
- podtato-head/podtato-head: Demo App for TAG App Delivery
-
Part-2: Evaluating Application Resiliency with Keptn and LitmusChaos (use-case and demo)
Automated deployment of an application via Keptn is typically chained with CI pipelines that generate the images or resource artifacts. In our use-case, the goal is to examine the resilience of one such helloservice application: the CNCF podtato-head. The hypothesis as a developer or user of the helloservice is that (a) the app is nearly always available and (b) accessed within a desired latency. We shall use a pod-kill chaos experiment to disrupt the state and verify if our resilience hypothesis holds true (i.e., whether the service has been built/deployed to meet our expectations). This action is performed when the application is busy serving requests, as this is a real-world case.
-
Modern continuous delivery on Kubernetes for developers
git clone https://github.com/cncf/podtato-head.git
litmus
-
12 Months of Rust, 50k+ changed lines of code, 8 design iterations. The extent of writing an async ASGI web server in Rust for Python for a 10% performance increase.
TL;DR: pyre is an async server written in Rust that gives big benchmark performance increases but minimal real-world improvements so take benchmarks as a grain of salt and respect the performance existing servers give :P
What are some alternatives?
keptn - Cloud-native application life-cycle orchestration. Keptn automates your SLO-driven multi-stage delivery and operations & remediation of your applications.
chaos-mesh - A Chaos Engineering Platform for Kubernetes.
litmus - Litmus helps SREs and developers practice chaos engineering in a Cloud-native way. Chaos experiments are published at the ChaosHub (https://hub.litmuschaos.io). Community notes is at https://hackmd.io/a4Zu_sH4TZGeih-xCimi3Q
chaosmonkey - Chaos Monkey is a resiliency tool that helps applications tolerate random instance failures.
spring-petclinic - A sample Spring-based application
ormsgpack - Msgpack serialization/deserialization library for Python, written in Rust using PyO3 and rust-msgpack. Reboot of orjson. msgpack.org[Python]
litmus-service - Integration for LitmusChaos
pyre-check - Performant type-checking for python.
prometheus-service - Keptn service for utilizing Prometheus monitoring and alerting in keptn
Kore - An easy to use, scalable and secure web application framework for writing web APIs in C or Python. || This is a read-only mirror, please see https://kore.io/mail and https://kore.io/source for information on how to contribute via the mailing lists.
Heimdall - An Application dashboard and launcher
Python-Regex - A port of the Rust regex library to python for super speed linear matching.