Struct SubdomainConfig 

pub struct SubdomainConfig {
    pub core: Vec<String>,
    pub supporting: Vec<String>,
    pub generic: Vec<String>,
}

DDD subdomain classification for volatility assessment

Based on Khononov’s Balanced Coupling model: volatility should be determined by business domain classification, not just git history.

• Core subdomains = High volatility (competitive advantage, constantly optimized)
• Supporting subdomains = Low volatility (boring CRUD/ETL, rarely changes)
• Generic subdomains = Low volatility (solved problems, stable implementations)

Fields

core: Vec<String>

Core subdomain modules (high volatility - competitive advantage)

supporting: Vec<String>

Supporting subdomain modules (low volatility - stable business logic)

generic: Vec<String>

Generic subdomain modules (low volatility - solved problems)

Trait Implementations

impl Clone for SubdomainConfig

fn clone(&self) -> SubdomainConfig

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for SubdomainConfig

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl Default for SubdomainConfig

fn default() -> SubdomainConfig

Returns the “default value” for a type.

impl<'de> Deserialize<'de> for SubdomainConfig

fn deserialize<__D>(__deserializer: __D) -> Result<Self, __D::Error>

where __D: Deserializer<'de>,

Deserialize this value from the given Serde deserializer.