In this section we will be taking a look at the MVVM pattern architecture and the communication between the components that make up the architecture.
The MVVM design pattern is designed to control the separation between the user interfaces (views), the ViewModels that contain the actual binding to the Model, and the models that contain the actual structure of the entities representing information stored on a database or from a web service.
The following screenshot shows the communication between each of the components contained within the MVVM design pattern architecture:
The MVVM design pattern is divided into three main areas, as you can see from the preceding screenshot, and these are explained in the following table:
MVVM type |
Description |
Model |
The Model is basically a representation of business related entities used by an application, and is responsible for fetching data from either a database, or web service, and then de-serialized... |