Netflix/rend
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 9 components.

handlers2293 LOC (27%) 15 files
orcas1615 LOC (19%) 5 files
client1600 LOC (19%) 13 files
protocol1257 LOC (15%) 10 files
metrics742 LOC (9%) 10 files
server347 LOC (4%) 4 files
common177 LOC (2%) 1 file
ROOT169 LOC (2%) 1 file
timer42 LOC (<1%) 4 files

scope details...
  • 63 files, 8,242 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.
ROOT132 commits (23%)
handlers125 commits (22%)
client74 commits (13%)
orcas73 commits (13%)
common73 commits (13%)
metrics73 commits (13%)
server49 commits (8%)
protocol10 commits (1%)
timer2 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 2015
server
10
39
timer
2
protocol
10
orcas
10
63
common
2
43
28
ROOT
8
80
44
handlers
37
88
client
11
41
22
metrics
5
68


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:12