[Project D] Devlog #4: More Reporting

Before we begin, if you want to catch up, you can read the previous entry in this series over here.

---

So, I'm still on reporting. Over the weekend, I decided to break down the tasks that I needed to do for the reporting clearly. Earlier in the week, a document was created that sought to harmonize the reporting each service needed to produce, which made it seem a bit too broad. So after spending some time breaking down the document, I now had a clear picture of what I needed to work on.

I had a discussion with one of my teammates and he raised a point that made me reconsider the initial design that I had (the naive approach). It was indeed naive, but it did serve its purpose. For now, I have a clearer picture of what I need to do to reduce the number of joins that need to be run for the reports. I enabled spring.jpa.show-sql in my application-dev.properties which showed me quite a lot of joins being run and while this is fine for my local database, I can see it becoming an issue in the production environment.

I will attempt to implement the new design that I have for the data that will need to be reported on so that it can reduce the number of joins and hopefully improve the performance of the app in that regard. Perhaps it might also simplify the queries.

That's about it for now (this might be the shortest devlog yet). Until next time, I bid you adieu.

Btw, I have a new project which I want to start soon, perhaps I'll write a devlog about it as well. Until then.