At first glance this article reads as a gratuituous buzzword soup with little to show regarding software architecture. After re-reading it, it still sounds lik

At first glance this article reads as a gratuituous buzzword soup with little to show regarding software architecture. After re-reading it, it still sounds like the author dumped all the buzzwords he could thought of, and the software architecture bit sounded like trying too hard to reinvent something like a generic layered architecture or even a Clean Architecture. A more generous interpretation is that this blog post proposes a specialized variant of a Clean Architecture, where the application layer is specialized to organize it's commands around feature-specific behavior. However, it also sounds like the author tried to reinvent the wheel without citing any prior work, which is very hard to explain. All in all, I think the article does not justify a click. Everyone is better off reading up on the classic architectures such as hexagonal architecture, layered architecture, and clean architecture. At least this path leads everyone to the exact same place without having to come up with ad-hoc names for well established concepts like application layer, business logic, use cases, etc.