Stack technologies tend to bound contexts based on technologies and not on ___domain boundaries.
This is why we see all these products targeted at companies with 24 microservices with 26 developers who have to run end to end testing on everything.
Architectural erosion is primarily a cultural issue and any tool that helps people discover and call out architectural violations is potentially useful.
Many companies can't just do the inverse Conway law, and if you look at the state of devops report, note how they call out CAB forums and controls being problematic for even high performing companies to become elite.
This product as an example, which just really means you want to keep k8s but have given up on loose coupling and high cohesion.
This is why we see all these products targeted at companies with 24 microservices with 26 developers who have to run end to end testing on everything.
Architectural erosion is primarily a cultural issue and any tool that helps people discover and call out architectural violations is potentially useful.
Many companies can't just do the inverse Conway law, and if you look at the state of devops report, note how they call out CAB forums and controls being problematic for even high performing companies to become elite.
This product as an example, which just really means you want to keep k8s but have given up on loose coupling and high cohesion.
https://www.signadot.com/blog/how-uber-and-doordash-enable-d...
Throwing products at structure problems typically doesn't work.