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

metacat-main10608 LOC (22%) 84 files
metacat-common-server10057 LOC (21%) 225 files
metacat-connector-hive7677 LOC (16%) 69 files
metacat-connector-polaris3435 LOC (7%) 47 files
metacat-common3125 LOC (6%) 85 files
metacat-connector-s32226 LOC (4%) 36 files
metacat-thrift2055 LOC (4%) 10 files
metacat-metadata-mysql1992 LOC (4%) 7 files
metacat-client1310 LOC (2%) 14 files
metacat-connector-cassandra746 LOC (1%) 10 files
metacat-connector-druid607 LOC (1%) 23 files
metacat-connector-jdbc580 LOC (1%) 8 files
metacat-connector-snowflake423 LOC (<1%) 7 files
metacat-connector-mysql401 LOC (<1%) 8 files
metacat-connector-postgresql375 LOC (<1%) 7 files
metacat-metadata321 LOC (<1%) 22 files
metacat-connector-redshift289 LOC (<1%) 7 files
metacat-iceberg-dto242 LOC (<1%) 3 files
metacat-connector-pig216 LOC (<1%) 5 files
codequality25 LOC (<1%) 1 file
metacat-war21 LOC (<1%) 2 files

scope details...
  • 680 files, 46,731 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.
metacat-main225 commits (34%)
metacat-common-server160 commits (24%)
metacat-connector-hive155 commits (23%)
metacat-common94 commits (14%)
metacat-connector-polaris66 commits (10%)
metacat-thrift53 commits (8%)
metacat-client38 commits (5%)
metacat-metadata-mysql34 commits (5%)
metacat-connector-jdbc32 commits (4%)
metacat-connector-mysql21 commits (3%)
metacat-connector-postgresql18 commits (2%)
metacat-connector-redshift17 commits (2%)
metacat-connector-s315 commits (2%)
metacat-connector-snowflake13 commits (2%)
metacat-connector-cassandra13 commits (2%)
metacat-connector-pig12 commits (1%)
metacat-connector-druid11 commits (1%)
codequality5 commits (<1%)
metacat-metadata4 commits (<1%)
metacat-war4 commits (<1%)
metacat-iceberg-dto2 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
metacat-main
6
18
5
22
4
12
14
16
31
60
37
metacat-connector-polaris
8
13
4
7
12
22
metacat-common-server
11
9
12
6
4
15
10
15
27
43
8
metacat-connector-hive
5
5
7
6
10
9
12
24
27
50
metacat-common
6
4
2
5
1
9
2
10
16
27
12
metacat-iceberg-dto
2
metacat-thrift
2
1
1
1
4
11
15
18
metacat-client
2
2
1
1
2
4
4
5
10
7
metacat-metadata-mysql
1
1
8
2
5
4
8
5
metacat-connector-druid
2
1
2
2
2
2
metacat-connector-snowflake
1
2
1
1
8
metacat-metadata
1
1
2
metacat-connector-cassandra
1
1
11
metacat-connector-jdbc
1
4
1
1
7
18
metacat-connector-postgresql
1
1
16
metacat-connector-s3
1
1
3
10
metacat-connector-redshift
1
16
metacat-connector-pig
4
8
codequality
1
1
2
1
metacat-war
1
3
metacat-connector-mysql
4
17


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["metacat-connector-polaris"]
    n1["metacat-connector-hive"]
    n2["metacat-common"]
    n3["metacat-main"]
    n4["metacat-common-server"]
    n5["metacat-iceberg-dto"]
    n0 ---|"6"| n0
    n1 ---|"3"| n2
    n0 ---|"3"| n1
    n3 ---|"2"| n3
    n1 ---|"2"| n1
    n4 ---|"2"| n4
    n2 ---|"2"| n4
    n1 ---|"2"| n4
    n4 ---|"2"| n3
    n4 ---|"2"| n0
    n4 ---|"1"| n5
    n2 ---|"1"| n5
    n1 ---|"1"| n5
    n5 ---|"1"| n5
    n0 ---|"1"| n3
    n0 ---|"1"| n2
    classDef default fill:#00b2ee,stroke:#ffffff,color:#000000;
    classDef highlighted fill:#00b2ee,stroke:#ffffff,color:#000000;
    linkStyle 0 stroke:#a0a0a0B7,stroke-width:6px
    linkStyle 1 stroke:#00688b82,stroke-width:3px
    linkStyle 2 stroke:#00688b82,stroke-width:3px
    linkStyle 3 stroke:#a0a0a070,stroke-width:2px
    linkStyle 4 stroke:#a0a0a070,stroke-width:2px
    linkStyle 5 stroke:#a0a0a070,stroke-width:2px
    linkStyle 6 stroke:#00688b70,stroke-width:2px
    linkStyle 7 stroke:#00688b70,stroke-width:2px
    linkStyle 8 stroke:#00688b70,stroke-width:2px
    linkStyle 9 stroke:#00688b70,stroke-width:2px
    linkStyle 10 stroke:#00688b5E,stroke-width:1px
    linkStyle 11 stroke:#00688b5E,stroke-width:1px
    linkStyle 12 stroke:#00688b5E,stroke-width:1px
    linkStyle 13 stroke:#a0a0a05E,stroke-width:1px
    linkStyle 14 stroke:#00688b5E,stroke-width:1px
    linkStyle 15 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:32