Netflix/atlas
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 22 components.

atlas-core16153 LOC (43%) 157 files
atlas-eval3952 LOC (10%) 49 files
atlas-chart3939 LOC (10%) 59 files
atlas-pekko2589 LOC (6%) 33 files
atlas-lsp2385 LOC (6%) 12 files
atlas-jmh2291 LOC (6%) 43 files
atlas-webapi1390 LOC (3%) 12 files
atlas-lwc-events1144 LOC (3%) 12 files
atlas-postgres1070 LOC (2%) 9 files
atlas-lwcapi1033 LOC (2%) 15 files
atlas-json3306 LOC (<1%) 5 files
project293 LOC (<1%) 5 files
atlas-lspapi98 LOC (<1%) 2 files
atlas-spring-pekko77 LOC (<1%) 3 files
conf61 LOC (<1%) 1 file
atlas-standalone55 LOC (<1%) 2 files
atlas-spring-lwc-events48 LOC (<1%) 1 file
atlas-spring-eval39 LOC (<1%) 1 file
atlas-spring-lwcapi30 LOC (<1%) 1 file
atlas-spring-webapi20 LOC (<1%) 1 file
atlas-pekko-testkit14 LOC (<1%) 1 file
.github7 LOC (<1%) 1 file

scope details...
  • 425 files, 36,994 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.
project1177 commits (38%)
atlas-core589 commits (19%)
atlas-eval250 commits (8%)
atlas-webapi227 commits (7%)
atlas-chart208 commits (6%)
atlas-lwcapi140 commits (4%)
atlas-jmh86 commits (2%)
atlas-standalone49 commits (1%)
atlas-pekko45 commits (1%)
atlas-lwc-events45 commits (1%)
atlas-postgres15 commits (<1%)
atlas-spring-lwc-events10 commits (<1%)
atlas-spring-eval7 commits (<1%)
atlas-lsp7 commits (<1%)
atlas-spring-webapi6 commits (<1%)
atlas-spring-pekko5 commits (<1%)
atlas-spring-lwcapi5 commits (<1%)
atlas-pekko-testkit4 commits (<1%)
atlas-lspapi4 commits (<1%)
conf2 commits (<1%)
atlas-json31 commits (<1%)
.github1 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
project
84
109
88
87
95
112
106
105
86
105
101
87
12
atlas-core
62
32
31
20
27
57
24
30
41
56
81
124
4
atlas-eval
22
15
47
17
22
17
29
17
36
28
atlas-pekko
27
5
10
3
atlas-lwcapi
8
14
19
9
16
11
13
5
21
22
2
atlas-webapi
16
5
3
7
15
6
14
7
12
21
38
81
2
atlas-chart
11
9
6
12
7
6
10
11
9
7
35
85
atlas-jmh
15
2
6
5
5
7
3
4
9
8
12
10
atlas-lwc-events
4
10
26
5
atlas-lsp
7
atlas-postgres
3
3
3
2
3
1
atlas-lspapi
4
atlas-spring-lwc-events
1
3
3
3
atlas-pekko-testkit
1
1
1
1
atlas-spring-pekko
1
1
1
2
atlas-spring-eval
1
1
1
3
1
atlas-spring-lwcapi
1
1
1
1
1
atlas-standalone
1
1
2
1
2
2
3
1
1
6
7
22
atlas-spring-webapi
1
1
1
1
2
atlas-json3
1
.github
1
conf
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... 

flowchart TB
    n0["atlas-core"]
    n1["atlas-jmh"]
    n2["atlas-pekko"]
    n3["atlas-eval"]
    n4["atlas-webapi"]
    n5["atlas-chart"]
    n6["project"]
    n7["atlas-lsp"]
    n8["atlas-lspapi"]
    n0 ---|"20"| n0
    n1 ---|"11"| n0
    n2 ---|"7"| n2
    n3 ---|"5"| n0
    n0 ---|"4"| n4
    n4 ---|"3"| n4
    n5 ---|"3"| n0
    n0 ---|"3"| n6
    n7 ---|"3"| n0
    n3 ---|"3"| n3
    n5 ---|"3"| n6
    n3 ---|"2"| n6
    n8 ---|"2"| n7
    n5 ---|"2"| n4
    n7 ---|"2"| n4
    n7 ---|"2"| n5
    n6 ---|"2"| n6
    n5 ---|"2"| n3
    n1 ---|"2"| n1
    n1 ---|"2"| n4
    n7 ---|"1"| n7
    n2 ---|"1"| n6
    n2 ---|"1"| n4
    n6 ---|"1"| n4
    n6 ---|"1"| n7
    n3 ---|"1"| n4
    classDef default fill:#00b2ee,stroke:#ffffff,color:#000000;
    classDef highlighted fill:#00b2ee,stroke:#ffffff,color:#000000;
    linkStyle 0 stroke:#a0a0a0FF,stroke-width:10px
    linkStyle 1 stroke:#00688bA5,stroke-width:5px
    linkStyle 2 stroke:#a0a0a082,stroke-width:3px
    linkStyle 3 stroke:#00688b70,stroke-width:2px
    linkStyle 4 stroke:#00688b70,stroke-width:2px
    linkStyle 5 stroke:#a0a0a05E,stroke-width:1px
    linkStyle 6 stroke:#00688b5E,stroke-width:1px
    linkStyle 7 stroke:#00688b5E,stroke-width:1px
    linkStyle 8 stroke:#00688b5E,stroke-width:1px
    linkStyle 9 stroke:#a0a0a05E,stroke-width:1px
    linkStyle 10 stroke:#00688b5E,stroke-width:1px
    linkStyle 11 stroke:#00688b5E,stroke-width:1px
    linkStyle 12 stroke:#00688b5E,stroke-width:1px
    linkStyle 13 stroke:#00688b5E,stroke-width:1px
    linkStyle 14 stroke:#00688b5E,stroke-width:1px
    linkStyle 15 stroke:#00688b5E,stroke-width:1px
    linkStyle 16 stroke:#a0a0a05E,stroke-width:1px
    linkStyle 17 stroke:#00688b5E,stroke-width:1px
    linkStyle 18 stroke:#a0a0a05E,stroke-width:1px
    linkStyle 19 stroke:#00688b5E,stroke-width:1px
    linkStyle 20 stroke:#a0a0a04C,stroke-width:1px
    linkStyle 21 stroke:#00688b4C,stroke-width:1px
    linkStyle 22 stroke:#00688b4C,stroke-width:1px
    linkStyle 23 stroke:#00688b4C,stroke-width:1px
    linkStyle 24 stroke:#00688b4C,stroke-width:1px
    linkStyle 25 stroke:#00688b4C,stroke-width:1px
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 17:32