Controllers and views need to work with data that comes from HTTP requests. For example, routes may provide a key that identifies a record, and posted form FIELDS may provide model properties. The process of converting these string values to .NET objects could be complicated and something that you have to do with each request. Model binding automates and simplifies this process. 

The model binding system fetches the data from multiple sources such as form fields, route data, and query strings. It also provides the data to controllers and views in method parameters and properties, converting plain string data to .NET objects and types in the process.

Example:
Let’s say you have the following action method on the PostsController class:

And the app receives a request with this URL:

After the routing selects the action method, model binding EXECUTES the following steps.

• Locate the first parameter of GetByID, an integer named id, look through the available sources in the HTTP request and find id = "5" in route data.
• Convert the string "5" into an integer 5.
• Find the next parameter of GetByID, a boolean named archivedOnly.
• Look through the sources and find "ArchivedOnly=true" in the query string. It ignores the case when matching the parameters to the strings.
• Convert the string "true" into boolean true.

Some other examples of attributes include:
1. [FromQuery] - Gets values from the query string.
2. [FromRoute] - Gets values from route data.
3. [FromForm] - Gets values from posted form fields.
4. [FromBody] - Gets values from the request body.
5. [FromHeader] - Gets values from HTTP HEADERS.