Barbacane FAQs

Question 1

Can Barbacane's functionality be extended?

Accepted Answer

Yes, Barbacane is highly extensible. Developers can write custom plugins in any WebAssembly-compatible language to add bespoke routing logic, middleware, or integrations, all running securely in a sandbox.

Question 2

Is Barbacane suitable for edge deployments?

Accepted Answer

Absolutely. Barbacane features an edge-ready architecture with stateless data plane instances designed to run close to your users, managed by a separate control plane for efficient compilation and distribution of configurations.

Question 3

What is Barbacane?

Accepted Answer

Barbacane is a high-performance, spec-driven API gateway built in Rust that uses your OpenAPI or AsyncAPI specifications as the single source of truth for routing, validation, and authentication.

Question 4

How does Barbacane utilize API specifications?

Accepted Answer

Barbacane transforms your existing OpenAPI 3.x or AsyncAPI 3.x specification into the gateway's configuration, eliminating proprietary languages and ensuring consistency between your spec and infrastructure.

Question 5

What are the core performance and security benefits of Barbacane?

Accepted Answer

Built on Rust, Tokio, and Hyper, Barbacane delivers high performance and predictable low latency. It's secure by default with a memory-safe runtime, TLS, and sandboxed WebAssembly (WASM) plugins.

Barbacane

Barbacane

Key Features

Use Cases

Key Features

Use Cases