Architecture Overview

Let’s explore what the architecture of our application is to look like.

We’ll keep this simple and just stick to the components and how they fit together, rather than start describing how it may look once deployed to a production environment.

The application we’re to build has three main components.

There’s the database component, which we’ll be using PostgreSQL. We’ll run this in Docker to make things easy.

Then there’s our backend component. This is the Spring Boot application we are to build.

Then there’s the frontend component, which is a React application that I provide for you. Of course, feel free to build your own if you so choose, there’s nothing to say that you need to use my one.

Although not standard UML, I’ve indicated that we’ll use JPA in our Spring Boot application as the means to communicate with the database.

The frontend component will communicate with the backend through a REST API.

The REST API represents the interface between the frontend and backend, and considering we’ve already got a frontend to work with, it’s important that we implement the correct endpoints.

Summary

• The app has a React frontend, Spring Boot backend and Postgres database component
• The frontend interacts with the backend via a REST API
• The backend interacts with the database using JPA