async-container

Async::Container

Provides containers which implement parallelism for clients and servers.

Features

• Supports multi-process, multi-thread and hybrid containers.
• Automatic scalability based on physical hardware.
• Direct integration with systemd using $NOTIFY_SOCKET.
• Internal process readiness protocol for handling state changes.
• Automatic restart of failed processes.

Usage

Please see the project documentation for more details.

• Getting Started - This guide explains how to use async-container to build basic scalable systems.

• Systemd Integration - This guide explains how to use async-container with systemd to manage your application as a service.

• Kubernetes Integration - This guide explains how to use async-container with Kubernetes to manage your application as a containerized service.

Releases

Please see the project releases for all releases.

v0.25.0

• Introduce async:container:notify:log:ready? task for detecting process readiness.

v0.24.0

• Add support for health check failure metrics.

v0.23.0

• Add support for NOTIFY_LOG for Kubernetes readiness probes.

v0.21.0

• Use SIGKILL/Thread#kill when the health check fails. In some cases, SIGTERM may not be sufficient to terminate a process because the signal can be ignored or the process may be in an uninterruptible state.

v0.20.1

• Fix compatibility between Async::Container::Hybrid and the health check.
• Async::Container::Generic#initialize passes unused arguments through to Async::Container::Group.

v0.20.0

• Improve container signal handling reliability by using Thread.handle_interrupt except at known safe points.
• Improved logging when child process fails and container startup.
• Add health_check_timeout for detecting hung processes.

Contributing

We welcome contributions to this project.

• Fork it.
• Create your feature branch (git checkout -b my-new-feature).
• Commit your changes (git commit -am 'Add some feature').
• Push to the branch (git push origin my-new-feature).
• Create new Pull Request.

Developer Certificate of Origin

In order to protect users of this project, we require all contributors to comply with the Developer Certificate of Origin. This ensures that all contributions are properly licensed and attributed.

Community Guidelines

This project is best served by a collaborative and respectful environment. Treat each other professionally, respect differing viewpoints, and engage constructively. Harassment, discrimination, or harmful behavior is not tolerated. Communicate clearly, listen actively, and support one another. If any issues arise, please inform the project maintainers.