Building a Full Stack Java Application Part II

This course is part 2 in our series, teaching you how to build a full-stack Java application, from nothing to fully functioning! In this course, we will continue the work from part 1, making the frontend much more flexible, adding a new advanced view with a query builder allowing for aggregation functions. On the backend, we will be adding in partitioning and expiry rules so that our tables self-regulate themselves over time. We also made the backend a bit more flexible to better work with our frontend.

Source Code for this code can be found on our GitHub page which is found in the resources section of our Introduction lecture.

The passage that follows is from Course 1:

Follow along with the course to create a full stack log viewer app – from beginning to end. The application utilizes Java in a variety of ways to build out a logging app: native Java to interface with the NoSQL database (GridDB), JDBC to interface with the db using SQL, Spring Boot to build out a REST API, and finally JSON Parsing & HTTP requests with Java. Lastly, outside of Java, there is also some react.js for the frontend to query the Spring Boot backend and to create our data tables of our logs.

The basic premise of the app is split up into three parts: the log agent, the log processor, and the log viewer. The log agent is responsible for monitoring the host machine for logs of the user’s choosing. When it finds new data, it saves the raw logs into GridDB (the database of choice). Then, the log processor scans the db and finds new rows of raw logs, processes the data into proper fields (set by the user) and re-saves them into the database into a new table. And finally, the log viewer queries the database. The log viewer is comprised of a backend (Spring Boot) REST API, and a frontend (react.js) to view the parsed log data.