Plugins

Install only what you need

loadr ships a small core. Heavy protocol drivers are delivered as runtime plugins — they load at runtime, on demand, and are never baked into the binary. One loadr plugin install <name> pulls a driver from the signed index, then a request to its URL scheme just works.

Resolved from a signed index SHA-256 verified ABI-checked at load

Database

3 plugins

Relational and document stores — the query (or operation) is the request.

M

MongoDB

mongodb://

Insert, find, update, aggregate and command — one operation per request, on the official Mongo driver.

DatabaseView plugin →
P

PostgreSQL

postgres://

Parameterised SELECT / INSERT / UPDATE bound with $1, $2 … and pooled per VU via sqlx.

DatabaseView plugin →
M

MySQL

mysql://

One query per request over the MySQL wire protocol, safely bound and pooled per VU.

DatabaseView plugin →

Cache

1 plugin

Key/value and in-memory stores driven at their native wire protocol.

R

Redis

redis://

Speak RESP over TCP — SET, GET, INCR, EXPIRE and the rest, one command per request.

CacheView plugin →

Messaging

2 plugins

Brokers and queues — produce, publish, fetch and consume.

A

Apache Kafka

kafka://

Produce and fetch against a broker, one operation per request — pure-Rust, no librdkafka.

MessagingView plugin →
R

RabbitMQ

amqp://

Publish and consume over AMQP 0.9.1, declaring queues inline — the pure-Rust lapin client.

MessagingView plugin →

Search

1 plugin

Search and analytics engines over their HTTP/JSON APIs.

E

Elasticsearch

elasticsearch://

Index, get, search and bulk over the HTTP/JSON API — on loadr's own hyper stack.

SearchView plugin →

How install works

Resolve, verify, load

loadr plugin install <name> resolves the name in a signed plugin index — a versioned JSON catalogue that maps a short name to the right per-platform artifact. loadr picks the artifact for your host target, checks its declared ABI against the one your build provides, downloads it, verifies its SHA-256 against the index, unpacks it and installs it under your plugins directory. The native loader re-checks the abi_stable layout at load time as a second line of defence.

Find & install from the index
# search the catalogue, then install for this host
$ loadr plugin search mongo
$ loadr plugin install mongo
resolved mongo 1.1.0 (x86_64-unknown-linux-gnu)
sha256 verified ✓   abi 1.0 ✓
installed → ~/.loadr/plugins/mongo
Pin, update, inspect
# pin a version or override the host target
$ loadr plugin install postgres --version 1.1.0
# re-install newer, ABI-compatible builds
$ loadr plugin update
# list / inspect what's installed
$ loadr plugin list
$ loadr plugin info mysql

Full reference: Installing plugins · Plugin overview

Write your own plugin

The same model is open to you. Ship a new protocol, output or helper as a native (abi_stable) or WASM plugin, declare its URL schemes, publish it to an index — and anyone can loadr plugin install it.

Write your own → Publish to an index