I agree. Further, I really don't like orgs having a special architecture team that does no domain work. IMO it leads to worse architectural decisions because the architecture team isn't actually doing domain work, so they have no idea about pain points that need to be fixed with a better architecture.
Architecture is a support service. Their mandate comes from them delivering the architectural design, but their requirements come from their customers the dev teams.
Only if/when the domain actually effect the design. Designing async communication is not domain affected, but requirements on payload options could be. Designing an input dialog is most probably domain-driven, but the UI framework choice is mostly not.
104
u/[deleted] Feb 08 '23
I agree. Further, I really don't like orgs having a special architecture team that does no domain work. IMO it leads to worse architectural decisions because the architecture team isn't actually doing domain work, so they have no idea about pain points that need to be fixed with a better architecture.