dragonflydb/dragonfly · Architecture
A static read of how dragonflydb/dragonfly is wired together — module coupling, layering, and circular dependencies — derived from its import graph.
A
Architecture grade
score 100/100
0
Import cycles
lower is better
103
Modules parsed
149 edges
100%
Layeredness
clean-layer ratio
Most-depended-on modules
These are the highest-fan-in files — change them and the blast radius is largest. Read them first.
- tests/dragonfly/instance.py35 importers · radius 36
- tests/dragonfly/__init__.py32 importers · radius 32
- tests/dragonfly/utility.py27 importers · radius 29
- tests/dragonfly/seeder/__init__.py13 importers · radius 15
- tests/fakeredis/test/test_hypothesis/base.py9 importers · radius 10
- tests/dragonfly/cluster_test_utils.py7 importers · radius 7
- tests/dragonfly/replication_utils.py6 importers · radius 6
- tests/fakeredis/test/test_hypothesis/test_string.py4 importers · radius 4
Modules (5)
Source directories grouped from the import graph. Each links to a per-module page with its files and how it couples to the rest.
- tests/dragonfly42 files · 109 in-degree
- tests/fakeredis/test/test_hypothesis11 files · 21 in-degree
- tests/fakeredis/test3 files · 5 in-degree
- tests/dragonfly/valkey_search3 files · 1 in-degree
- tests/fakeredis/test/test_mixins3 files · 0 in-degree
Ask AI about dragonflydb/dragonfly
Grounded in the actual source code. Pick a starter question or write your own.
What does this repo do, in one paragraph?How would I get started using it?What are the main alternatives?Show me the entry point.
Or write your own questionInformational only. RepoPilot summarises public signals at the time of analysis; they can be incomplete or stale. Not professional, security, or legal advice.