Netflix/chaosmonkey
Logical Components
An overview of source code logical components.

Logical Decomposition #1: PRIMARY

The decompositions is based on the folder structure at level 1 (relative to the source code root).

Bubble Chart | Tree Map
Component Sizes (Lines of Code)
The "primary" logical decomposition has 21 components.

spinnaker721 LOC (21%) 5 files
command657 LOC (19%) 13 files
config350 LOC (10%) 3 files
deploy346 LOC (10%) 4 files
mysql287 LOC (8%) 1 file
eligible176 LOC (5%) 1 file
schedule174 LOC (5%) 2 files
grp163 LOC (4%) 1 file
ROOT131 LOC (3%) 2 files
term131 LOC (3%) 2 files
tracker31 LOC (<1%) 1 file
migration28 LOC (<1%) 1 file
errorcounter21 LOC (<1%) 1 file
outage21 LOC (<1%) 1 file
decryptor21 LOC (<1%) 1 file
constrainer16 LOC (<1%) 1 file
env16 LOC (<1%) 1 file
cal15 LOC (<1%) 1 file
cmd13 LOC (<1%) 1 file
clock12 LOC (<1%) 1 file
schedstore11 LOC (<1%) 1 file

scope details...
  • 45 files, 3,341 LOC (100.0% vs. main code).
Component Commits
Components ordered by number of commits
Total Commits per Component
All commits, some commits may include files from multiple components.
spinnaker28 commits (17%)
command28 commits (17%)
config17 commits (10%)
mysql15 commits (9%)
eligible9 commits (5%)
deploy7 commits (4%)
schedule7 commits (4%)
term7 commits (4%)
ROOT6 commits (3%)
tracker5 commits (3%)
cmd5 commits (3%)
constrainer5 commits (3%)
outage3 commits (1%)
env3 commits (1%)
decryptor3 commits (1%)
schedstore3 commits (1%)
errorcounter3 commits (1%)
grp2 commits (1%)
cal2 commits (1%)
migration2 commits (1%)
Yearly File Updates Trend per Components
The number of file changes in commits
animated commit history: all time cumulative | 12 months window
2026 2025 2024 2023 2022 2021 2020 2019 2018 2017 2016
outage
1
2
spinnaker
1
9
12
6
grp
2
ROOT
6
env
1
2
command
1
12
15
cal
2
deploy
1
4
2
decryptor
1
2
schedule
2
1
2
2
eligible
1
6
2
migration
2
tracker
1
4
schedstore
1
2
mysql
3
2
1
9
term
1
4
2
cmd
1
4
config
1
8
8
errorcounter
1
2
constrainer
1
2
2


Dependencies between components in same commits (past 180 days)
The number on the lines shows the number of shared commits.
See detailed temporal dependencies report...

No temporal dependencies found.

About This Analysis

Logical decomposition is a representation of the organization of the main source code, where every and each file is put in exactly one logical component.

  • A software system can have one or more logical decompositions.
  • A logical decomposition can be defined in two ways in Sokrates.
  • First approach is based on the folders structure. Components are mapped to folders at defined folder depth relative to the source code root.
  • Second approach is based on explicit definition of each component. In such explicit definitions, components are explicitly named and their files are selected based on explicitly defined path and content filters.
  • A logical decomposition is considered invalid if a file is selected into two or more components. This constraint is introduced in order to facilitate measuring of dependencies among components.
  • Files not assigned to any component are put into a special "Unclassified" component.

2026-10-07 19:06