Too Long; Didn't Read
I wrote about CA topic last year and today I’m going to write out another part of it. CA is good to make the software architecture more succinctly and manageable, but the boilerplate codes are also huge (if you used to implement it you will get my point — a lot of requests, responses, interactors or use cases, interfaces, and classes need to be created, see my implementation at <a href="https://github.com/thangchung/blog-core" target="_blank">https://github.com/thangchung/blog-core</a>). Back in the time, when we implement <a href="https://martinfowler.com/bliki/CQRS.html" target="_blank">Command Query Responsibility Segregation</a> (<a href="https://cqrs.files.wordpress.com/2010/11/cqrs_documents.pdf" target="_blank">CQRS</a>) and <a href="http://codebetter.com/gregyoung/2010/02/20/why-use-event-sourcing/" target="_blank">Event Sourcing</a> (ES)patterns that will make many people feel unhappy with those of boilerplate codes. That’s a reason I research and write out what I know and learn about make CA more practical and maintainable ways.