Architecture Patterns

Choosing the correct architecture for your backend application is an important decision because you will get the most of it in a long shot.

Properly structured code that follows the same rules for each inner domain is easier to be read and maintain for you and other developers that would work with it. Better code you write at the start - less pain you get later when requirements will change.

App architectures help you write easily testable, extensible and decoupled code. It refers to the overall organization of your code in things like Responsibilities for each class, Folder organization, Structure of the code: network calls, responses, errors.

Some popular architecture patterns are:

• MVC
• MVVM
• Three-Tier
• Onion
• Hexagon

Model View Controller

Model View Controller, or MVC, refers to one of the most popular architectural patterns and the one from which many others derive.

Model: Your data classes.

• If you have User or Product objects, these model the real world.
• In Kotlin we use Data classes, while in Java they were called POJOs (Plain Old Java Object).
• Model layer is concerned with Business logic.
• It’s the backend that contains all the data logic.

View: Your visual classes.

• Everything the user sees falls under this category.