Member-only story
Do you really need entity classes?
Entities are boring, without them you can sometimes save time

A browser is a convenient tool for data visualization. In a browser, data can be presented in interactive charts or tables with relatively little effort.
One can choose any imaginable chart from many ready-to-use options (for example look at https://observablehq.com/@d3/gallery or https://plotly.com/javascript/). So in companies, it is common to use custom web applications for monitoring and data analysis.
The backend of a web application can be written in any language. Java has some advantages over other options. If a preconfigured application server, e.g. Tomcat, is used, the deployment is easy. If the backend only relays the data between the database and the authorized users, its development is quick.
Imagine an application displaying statistics derived from a data warehouse — it displays the results of many SQL queries. The application has to be frequently refined according to new business needs. Would it need some kind of individual class for loading and serializing the results of each query?
When the results of a query are joined products that have to be converted into arrays of objects containing collections of nested objects, entities with JPA queries produce the shortest…