Search Results for "requirements"

faasd is OpenFaaS reimagined but without the cost and complexity of Kubernetes. It runs on a single host with very modest requirements, making it fast and easy to manage. Under the hood it uses containers and Container Networking Interface (CNI) along with the same core OpenFaaS components from the main project. To deploy microservices and functions that you can update and monitor remotely. When you don't have the bandwidth to learn or manage Kubernetes. To deploy embedded apps in IoT and edge use-cases. ...

A *nix cross-platform (OS agnostic) supervisor. The main idea behind immortal is to keep up and running services forever even if the server is rebooted the service should be started and based on the requirements probably the services may start in sequence by waiting for others to start, wait some seconds before starting, etc, but at the end the idea remains, “run something forever” and in case exist just restart it. Doing this could be tricky, mainly because if you just want to launch your service/worker/daemon, etc you may not want to spend to much time understanding how to properly launch something in the operating system your company is using. ...

mango is a free, open source, lightweight HTTP Client library written entirely in C. The focus of the mango implementation is to reduce resource usage while still providing an almost full-scale HTTP Client. This makes it suitable for use in memory-constrained embedded devices where memory and CPU power are at a premium.

A peer-to-peer system designed to support the distribution of large files from web servers in a manner that is transparent to both web server and http client software, while dramatically reducing server bandwidth requirements.