In the previous chapter, we continued our exploration of Kotlin as a viable language for the creation of web applications by commencing the building of the Place Reviewer website. We began the chapter by discussing the Model-View-Controller design pattern and taking a high-level look at the primary components at play in MVC applications: the model, the view, and the controller. Once we had a clear understanding of the MVC design pattern and how it works, we commenced with the design and implementations of the backend for the Place Reviewer application.

First and foremost, we identified and clearly stated the anticipated use cases for our application. Next, we identified the data required to build an application that facilitates the use cases identified. After identification of the data to be catered for, we went full steam ahead with the development of the backend. We set up a Postgres database with which our application will communicate, then implemented the necessary entities and models for our application.

Further into the chapter, we discovered how to secure our application—authentication-wise—with Spring Security, this time without the use of JWTs. Finally, we learned how to create controllers for Spring MVC-based applications, as well as how to manage server logs with the ELK stack.

In this chapter, we shall finish up the creation of the Place Reviewer application by implementing its frontend. In the process of doing this, we shall learn about the following:

• Working with the Google Places API
• Application testing
• Deploying web applications to AWS

Let's get straight into this chapter by implementing the views for our application.