MVC encapsulation and decoupling 2. MVP architecture 3. MVVM architecture
The architecture is designed for high cohesion, low coupling and lower maintenance costs. Using schemas does not reduce the amount of code
MVC encapsulation and decoupling
In the process of use often use View SetModel call, here is the problem of coupling degree first thing to do is fat Controller, a heavy solution. Vc overweight analysis: 1, heavy UI 2, long-winded business logic 3, very long network layer 4, agent and so on…. Instead, focus only on dependencies and peel off the business layer. (Data layer business layer) two, decoupling (stripping UI layer) leads to protocol-oriented programming