misp-cloud VS Cake-Resque

Compare misp-cloud vs Cake-Resque and see what are their differences.

misp-cloud

misp-cloud - Cloud-ready images of MISP (by MISP)

Cake-Resque

Resque plugin for CakePHP : for creating background jobs that can be processed offline later (by wa0x6e)
Our great sponsors
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • WorkOS - The modern identity platform for B2B SaaS
  • SaaSHub - Software Alternatives and Reviews
misp-cloud Cake-Resque
1 1
68 159
- -
2.6 10.0
over 1 year ago almost 2 years ago
Shell 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.

misp-cloud

Posts with mentions or reviews of misp-cloud. 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
    10 projects | dev.to | 17 Nov 2022
    The project misp-cloud is providing ready to use AWS AMI containing the MISP platform as well as all other external component on the same image. They may provide images for Azure and DigitalOcean in the future.

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
    10 projects | dev.to | 17 Nov 2022
    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-cloud and Cake-Resque you can also consider the following projects:

misp-helm-chart

misp-docker - A production ready Dockered MISP

docker-misp - A (nearly) production ready Dockered MISP

misp-container-frontend

misp-container-worker

MISP - MISP (core software) - Open Source Threat Intelligence and Sharing Platform

supervisor - Supervisor process control system for Unix (supervisord)