Netflix/iep
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 20 components.

iep-admin1651 LOC (24%) 24 files
iep-servergroups1040 LOC (15%) 7 files
iep-ses384 LOC (5%) 4 files
iep-spring-leader-dynamodb329 LOC (4%) 2 files
iep-spring-aws2327 LOC (4%) 2 files
iep-spring-userservice323 LOC (4%) 8 files
iep-leader-api316 LOC (4%) 6 files
iep-dynconfig291 LOC (4%) 6 files
iep-spring-leader-redis-cluster275 LOC (4%) 3 files
iep-launcher269 LOC (4%) 3 files
project250 LOC (3%) 5 files
iep-spring-admin211 LOC (3%) 3 files
iep-spring209 LOC (3%) 4 files
iep-service189 LOC (2%) 7 files
iep-spring-dynconfig160 LOC (2%) 3 files
iep-spring-leader151 LOC (2%) 2 files
iep-spring-atlas132 LOC (1%) 3 files
iep-spring-spectatord79 LOC (1%) 2 files
iep-spring-sbhealth29 LOC (<1%) 1 file
.github7 LOC (<1%) 1 file

scope details...
  • 96 files, 6,622 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.
project1024 commits (55%)
iep-admin37 commits (2%)
iep-service30 commits (1%)
iep-launcher25 commits (1%)
iep-servergroups24 commits (1%)
iep-ses23 commits (1%)
iep-spring13 commits (<1%)
iep-spring-atlas11 commits (<1%)
iep-leader-api10 commits (<1%)
iep-spring-admin9 commits (<1%)
iep-spring-aws29 commits (<1%)
iep-spring-leader-redis-cluster8 commits (<1%)
iep-spring-leader8 commits (<1%)
iep-spring-dynconfig8 commits (<1%)
iep-spring-spectatord7 commits (<1%)
iep-spring-leader-dynamodb7 commits (<1%)
iep-spring-userservice7 commits (<1%)
iep-dynconfig4 commits (<1%)
iep-spring-sbhealth3 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
57
87
68
76
69
82
96
82
84
66
97
159
1
iep-servergroups
5
1
3
2
3
2
3
5
iep-admin
4
1
3
6
2
1
2
4
2
4
8
iep-spring-leader-redis-cluster
3
1
1
3
iep-ses
2
1
1
2
1
1
4
4
4
1
2
iep-spring-admin
2
1
1
2
3
iep-spring-spectatord
2
1
1
2
1
iep-launcher
2
1
1
1
1
1
1
2
1
1
9
4
iep-spring-userservice
2
1
1
2
1
iep-service
1
2
1
3
1
1
1
2
1
2
11
4
iep-spring-leader
2
1
1
2
2
iep-spring-atlas
2
1
1
4
3
iep-spring-sbhealth
2
1
iep-spring
1
2
1
3
6
iep-dynconfig
1
1
1
1
iep-leader-api
1
1
1
2
1
1
1
2
iep-spring-leader-dynamodb
1
1
1
3
1
iep-spring-aws2
1
1
2
4
1
iep-spring-dynconfig
1
1
1
2
3
.github
1


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["project"]
    n1["iep-servergroups"]
    n2["iep-admin"]
    n3["iep-spring-admin"]
    n4["iep-spring-atlas"]
    n5["iep-spring-spectatord"]
    n0 ---|"1"| n0
    n1 ---|"1"| n1
    n2 ---|"1"| n2
    n3 ---|"1"| n2
    n4 ---|"1"| n0
    n5 ---|"1"| n0
    n5 ---|"1"| n4
    classDef default fill:#00b2ee,stroke:#ffffff,color:#000000;
    classDef highlighted fill:#00b2ee,stroke:#ffffff,color:#000000;
    linkStyle 0 stroke:#a0a0a05E,stroke-width:1px
    linkStyle 1 stroke:#a0a0a05E,stroke-width:1px
    linkStyle 2 stroke:#a0a0a05E,stroke-width:1px
    linkStyle 3 stroke:#00688b5E,stroke-width:1px
    linkStyle 4 stroke:#00688b5E,stroke-width:1px
    linkStyle 5 stroke:#00688b5E,stroke-width:1px
    linkStyle 6 stroke:#00688b5E,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:31