Netflix/governator
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 10 components.

governator-legacy5860 LOC (47%) 84 files
governator-core3542 LOC (28%) 72 files
buildSrc944 LOC (7%) 3 files
governator-api480 LOC (3%) 43 files
governator-jetty373 LOC (3%) 7 files
governator-jersey309 LOC (2%) 4 files
governator-providers307 LOC (2%) 7 files
governator-commons-cli237 LOC (1%) 3 files
governator-archaius206 LOC (1%) 1 file
governator-servlet119 LOC (<1%) 4 files

scope details...
  • 228 files, 12,377 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.
governator-core215 commits (19%)
governator-legacy74 commits (6%)
governator-jetty42 commits (3%)
governator-servlet27 commits (2%)
governator-jersey24 commits (2%)
governator-api16 commits (1%)
governator-providers10 commits (<1%)
governator-archaius6 commits (<1%)
governator-commons-cli4 commits (<1%)
buildSrc3 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
governator-legacy
2
1
7
39
25
governator-servlet
13
10
4
governator-archaius
6
governator-commons-cli
4
governator-jetty
1
1
1
26
13
governator-providers
3
7
governator-api
14
2
governator-jersey
24
governator-core
2
2
4
13
115
74
5
buildSrc
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...

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