In this section, we will pick some performance issues and discuss them in more detail.
Here, the application developers usually lack a good understanding of the used framework capabilities so they use extra unnecessary logic that either produces extra database hits, memory consumption, or even processing power consumption. Such unwanted code can only be detected if it causes extra hits to resources or external calls, and the best way to detect this is to perform manual code inspection or profiling on the application.
If we open our project,
ExampleTwo, we will find a lot of good examples of extra unnecessary logic, such as loading the whole collection to search for an instance inside it, where ...