> I asked this question, because I do have doubts they exist. Especially, any modern one. It sounds like you don't do much, if any, professional work. > These

> I asked this question, because I do have doubts they exist. Especially, any modern one. It sounds like you don't do much, if any, professional work. > These architectures were introduced around 20 years ago to address technical shortcomings of enterprise systems at that time. No, not really, and your personal assertion completely misses the whole point of DDD or any software architectural style you mentioned. The whole point is to keep software flexible and accommodating of change, and in the process reflect a set of very basic software design principles that avoid/eliminate problems such as circular dependencies or testability. > Is any of the above a real pain in the project that you are building in 2022? Again, you don't seem to have much if any professional experience. UI testing, or any type of testing involving UI work either directly or indirectly such as accessibility/localization or any end-to-end test in general, is still an unsolved problem and a bane of software engineers. Nevertheless, your comment reads like a strawman. The main benefit, and the whole point, of layered architectures is to ensure the software architecture to simplify modifying/updating the bits that change very frequently and stabilize and minimize the need the fundamental bits that only rarely need to be touched. UIs tend to be the part of an application that is updated the most, thus it makes all the sense in the world to adopt a software architecture which handles UI as a separate external component which minimizes or eliminates both fan-in, and turns fan-out to be a non-issue by depending on abstract interfaces whose concrete implementations are injected. These are not dad's from the 1990s,these are fundamental software engineering concerns.