Additional info
Known issues
Current limitations, symptoms, and workarounds. This list will grow over time.
Overview
This page tracks known issues or limitations and suggests workarounds until fixes or improvements are shipped.
Issue index
Plugins fetch data independently, causing multiple database calls
Symptoms
- Multiple reads per request when several plugins are enabled
- Elevated latency under plugin-heavy configurations
- Higher database connection usage
Impact
- Increased end-to-end request latency
- Additional database load and connection churn
- Risk of slight read-time inconsistencies across plugins if data changes mid-request
Root cause
Plugins are intentionally independent and composable. There is no shared, request-scoped data loader/cache yet, so each plugin performs its own lookups.
Workarounds
- Keep the active plugin set minimal for your use case
- Prefer low-latency stores/backends in production
- Use connection pooling and close-to-app caches (for example, Redis) where applicable
- For custom plugins, accept a shared context object and reuse results written by other plugins
Status
Acknowledged. Improvements are planned to reduce duplicated reads across plugins.
Planned improvements
- Request-scoped data context for shared reads
- Optional per-request read-through cache to deduplicate lookups
- Plugin authoring guidance for coalescing reads when composing multiple plugins