I wish it had accessibility features like graphs on this dashboard: https://blog.cloudflare.com/project-a11y/
Alright, I think I have found the main point of our misunderstanding: > The main benefit, and the whole point, of layered architectures is to ensure the software architecture to simplify modifying/updating the bits that…
> To this day automated tests suits against UI tends to be flaky. So testing against a code api is indeed better. You don't need hexagonal architecture to test the code api. Layered architecture will do the job!
I asked specifically about "Hexagonal, Onion, or Clean architecture". CQRS is another story, it is relatively widely used and very handy in certain scenarios. Is LINE Pay designed in a form of some kind of onion…
> misses the whole point of DDD or any software architectural style you mentioned. I didn't mention DDD. > a set of very basic software design principles that avoid/eliminate problems such as circular dependencies or…
I wish it had accessibility features like graphs on this dashboard: https://blog.cloudflare.com/project-a11y/
Alright, I think I have found the main point of our misunderstanding: > The main benefit, and the whole point, of layered architectures is to ensure the software architecture to simplify modifying/updating the bits that…
> To this day automated tests suits against UI tends to be flaky. So testing against a code api is indeed better. You don't need hexagonal architecture to test the code api. Layered architecture will do the job!
I asked specifically about "Hexagonal, Onion, or Clean architecture". CQRS is another story, it is relatively widely used and very handy in certain scenarios. Is LINE Pay designed in a form of some kind of onion…
> misses the whole point of DDD or any software architectural style you mentioned. I didn't mention DDD. > a set of very basic software design principles that avoid/eliminate problems such as circular dependencies or…