Netflix/spark
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 18 components.

sql128709 LOC (39%) 937 files
core68283 LOC (20%) 594 files
mllib41197 LOC (12%) 304 files
python32843 LOC (10%) 96 files
common11399 LOC (3%) 148 files
streaming10453 LOC (3%) 111 files
resource-managers9730 LOC (2%) 82 files
graphx3081 LOC (<1%) 43 files
launcher2308 LOC (<1%) 20 files
dev1999 LOC (<1%) 12 files
mllib-local1896 LOC (<1%) 5 files
project1711 LOC (<1%) 3 files
licenses-binary748 LOC (<1%) 2 files
repl681 LOC (<1%) 6 files
ROOT235 LOC (<1%) 1 file
build148 LOC (<1%) 1 file
tools90 LOC (<1%) 1 file
R19 LOC (<1%) 1 file

scope details...
  • 2,367 files, 315,530 LOC (96.4% 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.
sql5505 commits (23%)
core4136 commits (17%)
python2121 commits (9%)
mllib1754 commits (7%)
project1194 commits (5%)
streaming635 commits (2%)
graphx219 commits (<1%)
common183 commits (<1%)
dev181 commits (<1%)
resource-managers168 commits (<1%)
repl113 commits (<1%)
launcher96 commits (<1%)
ROOT49 commits (<1%)
mllib-local30 commits (<1%)
tools21 commits (<1%)
build6 commits (<1%)
R1 commits (<1%)
licenses-binary1 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 2014 2013 2012 2011
python
49
272
259
452
555
281
253
ROOT
3
3
20
18
5
project
1
28
57
178
161
235
404
104
26
mllib-local
1
1
7
21
tools
5
5
11
sql
10
134
835
1149
1809
1221
347
resource-managers
10
63
93
2
core
50
289
433
686
924
1086
668
streaming
2
18
37
103
193
181
101
R
1
dev
2
25
28
52
50
24
common
9
33
60
81
mllib
12
104
213
479
625
258
63
build
1
4
1
repl
1
6
3
6
9
42
46
graphx
1
5
10
30
42
131
licenses-binary
1
launcher
11
21
28
36


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