Backend side architecture evolution (N-layered, DDD, Hexagon, Onion, Clean Architecture)
<p>Hola! So you want to be an architect, don't ya? Don’t lie to me, I know you do. Even if you don’t, you still want to be a better developer. Otherwise, you would not spend time reading this article </p>
<p>It is commendable. After all, we all want to be better if not the best in what we are doing. Here am I, to help you with that.</p>
<p>So, how do you become an architect? Obviously, by learning all the architectures! Of course, that is not true. You don’t need to know everything. You also don’t need to have experience with all of them. However, knowing at least the most popular ones, such as N-Layered, DDD, Hexagon, Onion, and Clean architecture; understanding their history, their usage, and the differences between those will definitely distinguish you from other developers.</p>
<p>I hope that was enough introduction words to engage you. If you are still interested, let’s get started </p>
<h1>Where it all began?</h1>
<p>Back in the good old days, there was no architecture at all. What blessing days were those. You could call yourself an architect only by knowing GoF patterns </p>
<p>However, computers became more powerful, the user’s demand increased which caused an application’s complexity to grow.</p>
<p><a href="https://medium.com/@iamprovidence/backend-side-architecture-evolution-n-layered-ddd-hexagon-onion-clean-architecture-643d72444ce4">Click Here</a></p>