Netflix/mantis
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.

mantis-control-plane40526 LOC (47%) 354 files
mantis-common7284 LOC (8%) 111 files
mantis-runtime7028 LOC (8%) 147 files
mantis-connectors4648 LOC (5%) 74 files
mantis-remote-observable3915 LOC (4%) 51 files
mantis-publish3794 LOC (4%) 58 files
mantis-runtime-autoscaler-api2804 LOC (3%) 36 files
mantis-server2778 LOC (3%) 30 files
mantis-network2660 LOC (3%) 29 files
mantis-runtime-executor2283 LOC (2%) 21 files
mantis-runtime-loader1081 LOC (1%) 18 files
mantis-source-jobs1035 LOC (1%) 19 files
mantis-client1001 LOC (1%) 10 files
mantis-rxcontrol925 LOC (1%) 23 files
mantis-jm-akka837 LOC (<1%) 7 files
mantis-examples766 LOC (<1%) 15 files
.baseline476 LOC (<1%) 1 file
mantis-discovery-proto333 LOC (<1%) 5 files
mantis-common-akka216 LOC (<1%) 5 files
mantis-common-serde39 LOC (<1%) 1 file
.github2 LOC (<1%) 1 file

scope details...
  • 1,016 files, 84,431 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.
mantis-control-plane321 commits (25%)
mantis-common99 commits (7%)
mantis-server70 commits (5%)
mantis-runtime60 commits (4%)
mantis-connectors42 commits (3%)
mantis-network27 commits (2%)
mantis-publish25 commits (2%)
mantis-runtime-loader23 commits (1%)
mantis-runtime-executor15 commits (1%)
mantis-client13 commits (1%)
mantis-examples7 commits (<1%)
mantis-source-jobs7 commits (<1%)
mantis-remote-observable6 commits (<1%)
mantis-runtime-autoscaler-api4 commits (<1%)
mantis-rxcontrol2 commits (<1%)
.baseline2 commits (<1%)
.github2 commits (<1%)
mantis-jm-akka2 commits (<1%)
mantis-common-serde2 commits (<1%)
mantis-common-akka1 commits (<1%)
mantis-discovery-proto1 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
mantis-control-plane
20
27
50
111
85
24
4
mantis-common
3
7
4
18
26
15
25
1
mantis-runtime
7
4
14
9
6
17
3
mantis-runtime-executor
6
9
mantis-runtime-autoscaler-api
1
3
mantis-network
4
1
3
5
3
6
5
mantis-server
3
10
34
7
4
12
mantis-connectors
2
3
5
8
2
22
mantis-publish
2
1
3
14
3
2
mantis-remote-observable
2
1
1
2
mantis-jm-akka
2
mantis-common-akka
1
mantis-examples
1
3
1
2
mantis-rxcontrol
2
.baseline
2
.github
2
mantis-source-jobs
1
2
1
1
2
mantis-discovery-proto
1
mantis-runtime-loader
12
8
3
mantis-common-serde
2
mantis-client
1
2
6
1
3


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["mantis-control-plane"]
    n1["mantis-common"]
    n0 ---|"3"| n0
    n0 ---|"2"| n1
    classDef default fill:#00b2ee,stroke:#ffffff,color:#000000;
    classDef highlighted fill:#00b2ee,stroke:#ffffff,color:#000000;
    linkStyle 0 stroke:#a0a0a082,stroke-width:3px
    linkStyle 1 stroke:#00688b70,stroke-width:2px
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:34