PRODPlataforma BaaS europeia soberanaAbra o painel →

Aurabase/benchmarks

Referências

Testes do mundo real em pilha completa — Portal de ferrugem +NATS +PostgreSQL

p95 < 9 ms @ 10 VUs0% errors @ 100 VUs379 req/s write throughput11× faster auth vs PocketBase

Medido no Docker local (máquina de desenvolvimento, Apple Silicon). Código-fonte dos benchmarks disponíveis em /benchmarks

02 — Read latency p95

p95 read latency by concurrency level (ms)

Supabase e Appwrite: estimativas baseadas em benchmarks publicados e problemas do GitHub. Linha verde = SLO de 200ms.

SLO 200ms1002003004005000senhora10 VUs50 VUs100 VUsAurabaseSupabaseAppwrite

03 — API overhead vs direct PostgreSQL

Sequential throughput (ops/s) — full stack vs direct PG query

1.000 iterações sequenciais, conexão Docker local. A sobrecarga é estrutural: gateway → NATS → db-service → PostgREST → PG.

list_509.0× sobrecarga
PG direto
2 438 /s
API
268 /s
point_read11.5× sobrecarga
PG direto
3 154 /s
API
292 /s
filtered2.6× sobrecarga
PG direto
414 /s
API
159 /s

Nota sobre filtrado (2,6×): A consulta filtrada (ORDER BY + WHERE) leva 2,35 ms no PG direto versus 0,3 ms para outros, o que comprime mecanicamente a taxa de sobrecarga aparente.

04 — Competitor comparison

Competitive benchmark — self-hosted stack under real conditions

PocketBase/TrailBase: SQLite (processo único, sem banco de dados de rede). Supabase: estimativas de pilha local. Appwrite: benchmark oficial do TTL.

StackArchitectureDBp95 read (10 VUs)p95 writep50 authScore
AurabaseRust + NATSPostgreSQL8.8 ms✓162 ms✓~15 ms✓
SupabaseGo + HaskellPostgreSQL~12 ms~~200 ms~~30 ms~
PocketBaseGo monoSQLite~7 ms✓~9 ms✓~300 ms✗
TrailBaseRust monoSQLite~1 ms✓~1 ms✓~200 ms✗
AppwritePHP + GoMariaDB~40 ms~~100 ms~~25 ms~
FirebaseCloudProprietary40–80 ms✗50–100 ms~~50 ms~
✓ compliant~ acceptable✗ exceeds SLO

05 — Level 1 Micro-benchmarks (Criterion.rs)

Critical functions in isolation — no infrastructure required

Argon2 hash

14 ms

10 max signups/IP/h

JWT generate

1.81µs

hot path × every request

JWT validate

1.58µs

hot path × every request

AES-GCM roundtrip

8.37µs

TOTP/MFA encryption

Filter parsing (×4)

226ns

parsing query params

JSON serde NatsReq

637ns

NATS message bus

06 — Auth GET /user under load

p95 auth latency — shared JWT token, 0% error across 3 concurrency tiers

10 VUs
50 VUs
100 VUs
Meta de SLO <200ms p95✓ 10 VUs, 50 VUs passam — 100 VUs sob pressão (174,8ms)

07 — CRUD Write (k6)

CREATE → UPDATE → DELETE scenario — 5→50 VUs, 2min

p50

51.7ms

p95

162ms

p99

216ms

throughput

379req/s

errors

0.00%

08 — Limits & context

PGRST_DB_POOL=20

PostgREST connection pool limit configured for local dev. In production with pool=100, saturation shifts to ~500 VUs. Configuration parameter, not architectural ceiling.

SQLite vs PostgreSQL

PocketBase and TrailBase (single-process SQLite) achieve lower raw latencies but do not support multi-tenancy or horizontal scaling.

Dev environment

All Aurabase tests run inside Docker on Apple Silicon dev hardware. On dedicated bare-metal servers, latencies are typically 20–40% lower.

Testes realizados em 29 de maio de 2026 · Pilha: Rust 1.87 · PostgreSQL 16 · k6 v2.0 · Criterion.rs 0.5 · Dados do concorrente provenientes de benchmarks oficiais publicados.