Skip to content
pubscout

Compare

The strongest value in each row is marked.

Attributeioredis

Redis client for Dart with connection pooling, pub/sub, transactions, and pipelining.

pub.devRemove
neat_cache

A cache abstraction for wrapping in-memory or redis caches with timeouts.

pub.devRemove
ScoresHealth74 (best)73
Maintenance96 (best)60
Quality93100 (best)
Popularity2752 (best)
Community5880 (best)
Compatibility8585
UsageDownloads (30 days)2.8k8.8k (best)
Likes929 (best)
Pub points150 / 160160 / 160 (best)
GitHub stars7512 (best)
MaintenanceLatest release3.2.1, 4 days ago (best)2.0.5, a year ago
Major versions in 12 months10 (best)
Contributors430 (best)
Publisherdartondox.devgoogle.dev
FitPlatformsAll (pure Dart)All (pure Dart)
WASM-readyNoNo
KindPure DartPure Dart
Code generationNoNo
Direct dependencies0 (best)5
LicenseMITAPACHE-2.0
Setup effortLowLow
JudgementStrengths
  • Supports pub/sub with both text and binary messages
  • Built-in connection pooling and auto-pipelining
  • Robust reconnection handling with retry strategies and handshake timeouts
  • Supports Redis URL configuration including TLS (rediss://)
  • Provides a clean abstraction over different cache providers like Redis.
  • Supports prefixes and codecs for easy data serialization and scoping.
Weaknesses
  • Requires a running Redis server network connection
  • Not an embedded local storage solution
  • Limited built-in provider options compared to larger caching libraries.
  • Testing Redis providers requires an external Redis instance.
WarningsNone
  • Quiet but busy
ioredis vs neat_cache: which Flutter package should you use? | pubscout