misp-helm-chart
By pburgisser
Cake-Resque
Resque plugin for CakePHP : for creating background jobs that can be processed offline later (by wa0x6e)
misp-helm-chart | Cake-Resque | |
---|---|---|
1 | 1 | |
0 | 159 | |
- | - | |
10.0 | 10.0 | |
over 1 year ago | almost 2 years ago | |
Smarty | PHP | |
- | MIT License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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.
misp-helm-chart
Posts with mentions or reviews of misp-helm-chart.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-11-17.
-
MISP at scale on Kubernetes
Helm chart: All the Kubernetes manifests were packaged into a helm chart
Cake-Resque
Posts with mentions or reviews of Cake-Resque.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-11-17.
-
MISP at scale on Kubernetes
Up to version 2.4.150, the MISP background jobs (workers) were managed by CakeResque library. When starting a worker, the MISP is writing its PID into Redis. Based on that PID, the frontend shows worker’s health by checking if the /proc/{PID} exists. When running multiple replicas, the last started pod writes its PIDs to Redis and may not be the same as the others. Refreshing the frontend on the browser may show an unavailable worker due to inconsistent PID numbers (for example, latest PID of process prio registered is 33 and the container serving the user’s request know process prio by its PID 55).
What are some alternatives?
When comparing misp-helm-chart and Cake-Resque you can also consider the following projects:
docker-misp - A (nearly) production ready Dockered MISP
misp-docker - A production ready Dockered MISP
misp-cloud - misp-cloud - Cloud-ready images of MISP
misp-container-worker
MISP - MISP (core software) - Open Source Threat Intelligence and Sharing Platform
misp-container-frontend
supervisor - Supervisor process control system for Unix (supervisord)
misp-helm-chart vs docker-misp
Cake-Resque vs misp-docker
misp-helm-chart vs misp-cloud
Cake-Resque vs misp-cloud
misp-helm-chart vs misp-container-worker
Cake-Resque vs docker-misp
misp-helm-chart vs misp-docker
Cake-Resque vs misp-container-worker
misp-helm-chart vs MISP
Cake-Resque vs MISP
misp-helm-chart vs misp-container-frontend
Cake-Resque vs supervisor