Architecture of Play Framework

In this section, we will discuss the typical architecture of a Play Framework web application. Here, some components are mandatory for all applications, such as the routes file, Controller, View Templates, and so on; some are optional:

We can observe the following steps in any Play Framework Web Application:

1. The users access a Play Web Application, using the application URL and a web browser.
2. When the user sends a HTTP request to a Play Web Application, such as /route2 in our example, first that request reaches the Play Framework's Routing component (the default route filename is routes). However, we can use any name. Some applications may have more than one route file; finally, they have one top-level routes file.

3. Play Framework Web Application's Route component decides who is responsible to handle that Request. It will find the correct mapping between the user who has submitted the HTTP request (using one of the HTTP request methods, such as GET or POST) and...