Let's talk about architecture Pattern Why I need to use it ?

it′s very important to define what is the architecture for the application that we're going to develop !! What do I mean by define? We need to design for maintainability, scalability, and how testable this application is going to be.

Lets Go !

 Many company started projects with the purpose of just develop the minimum product, but after spending time and resources on launching this application, you receive new features to develop, and that's when you came out and say: mmmm, I don′t want to touch that code, because maybe it's going to take a lot of time to refactoring, or even worse, to start everything from scratch. Here's when it became very important to define and design the architecture before starting developing the actual coding.

Many times we care about concerns, like business logic UI, everything else, so we want to have way to insert things in between these phases.

Just Imagine with This Example, you Will understand Why Architecture Pattern is very Important ?!

Imagine like you have like a store where you sell sandwiches, you don't want to have like everything already prepared, like the sandwich with ham, cheese, tomato, and everything inside the sandwich, I mean the reason like when we talk about architecture on a separated concern, it is more like having all the pieces separated by layers, like the bread, the ham, the cheese, and all, everything else, so because if somebody came to the place and asks you for a sandwich without the tomato, it would a little bit complicated just to, you know, go inside the sandwich and take the tomato out, it will be easier just to start putting all the layers and just give this to the person, so this will help us a lot to achieve our code much faster, it will be more easy to maintain, and it will more easy to scale, what I mean is that if you want to add like onions? You just put another layer, and if somebody ask you for that, it will be like just adding that to the sandwich, and that′s it!