Architecture_Patterns

Architecture patterns, also known as architectural styles or design patterns, are well-proven solutions to common problems in software architecture. These patterns provide templates or guidelines on how to structure software applications to manage complexities, enhance maintainability, improve performance, and ensure scalability and security. The choice of an appropriate architecture pattern can significantly influence the functionality, quality, and lifecycle of the Application.

Examples :

MVC, MVP, and MVVM are three popular design patterns in software development. Let’s have a look at them one by one.

all this Architecture has 3 layers and 2 layers View and Model are the same.

Model : Model means data that is required to display in the view. The model represents a collection of classes that describe the business logic (business model and the data model). It also defines the business rules for data, which means how the data can be changed and manipulated.

View : The View represents UI components like XML, HTML, etc. The view displays the data that is received from the controller as the outcome. In MVC pattern View monitors the model for any state change and displays the updated model. Model and View interact with each other using the Observer pattern.

The difference is the Translator :

• MVC Have Controller : The Controller is responsible for processing incoming requests. It processes the user’s data through the Model and passes back the results to View. It normally acts as a mediator between the View and the Model.

• MVP Have Presenter : The Presenter receives the input from users via View, then processes the user’s data with the help of Model and passes the results back to the View. The presenter communicates with the view through an interface. The interface is defined in the presenter class, to which it passes the required data. Activity/fragment or any other view component implements this interface and renders the data in a way they want. In the MVP design pattern, the presenter manipulates the model and also updates the view. In MVP View and Presenter are completely decoupled from each other’s and communicate with each other’s by an interface. Because decoupling mocking of the view is easier and unit testing of applications that leverage the MVP design pattern over the MVC design pattern is much easier.

• MVC Have ViewModel : It is responsible for exposing methods, commands, and other properties that help to maintain the state of the view, manipulate the model as the result of actions on the view, and trigger events in the view itself. View has a reference to View-Model but View-Model has no information about the View. There is a many-to-one relationship between View and View-Model, which means many Views can be mapped to one View-Model. It is completely independent of Views. The bi-directional data binding or the two-way data binding between the view and the View-Model ensures that the models and properties in the View-Model is in sync with the view. The MVVM design pattern is well suited to applications that need support for bi-directional data binding.

Code Example :

1. Clone the Repository:

   git clone https://github.com/Koru-zed/Architecture_Patterns.git

2. Navigate to the Project Directory:

   cd Achitecture_Patterns

3. Install Dependencies:

   flutter pub get

4. Run the App:

   flutter run