Bunkr
  • What is Bunkr
  • Getting Started
    • Start Exploring
    • Quick Start
  • Organizations
    • What is an organization?
    • Create an organization
    • Collaboration
      • Member Roles
    • Settings
  • Agents
    • What is an agent?
    • Installation
  • Pricing
    • Free Trial
    • Plans
  • Resources
    • Use Cases
      • Storage Routing
      • High-Availability
    • FAQ
Powered by GitBook
On this page
  • Architecture
  • Horizontal Scaling
  • Stateless and Disposable

Was this helpful?

  1. Agents

What is an agent?

PreviousSettingsNextInstallation

Last updated 4 years ago

Was this helpful?

Bunkr agents are lightweight software deployed at the edge of your infrastructure.

They proxy storage requests from your application to your configured storage providers by complying to storage location constraints you've defined.

Agents keep an opened connection with the control plane for real-time updates. This allows us to push changes you've made from the control plane into your agents.

Tips: Agents are automatically registered in the control plane when they connect.

Architecture

Bunkr agent's architecture is designed along several guiding principles:

  • Minimal dependencies

  • Runs everywhere

  • Scales without effort

  • Fallbacks to sane defaults

Our agents leans on principles and is designed to run best on Container Orchestration Systems such as Kubernetes, CloudFoundry, OpenShift, and similar projects.

Horizontal Scaling

Bunkr agents scale without the need for any additional external service dependencies (e.g. etcd, memcached, etc.). Scaling horizontally is as easy as starting another process.

Stateless and Disposable

Bunkr agents are stateless and share-nothing. The processes are disposable, meaning they can be started or stopped at a moment's notice. This facilitates fast elastic scaling, rapid deployment of code or config changes, and robustness of production deployments.

Bunkr agents strive to minimize startup time, taking no more than a few milliseconds to be up and ready to accept traffic. The processes shut down gracefully upon receiving a SIGTERM signal from the process manager.

The Twelve-Factor