The problem with the current database existing right now is that it is being improperly implemented. Some cases include: No singleton type pattern, bad use of HashMaps, and an overall bad design for the bridge-cross way between API and DB.
The Fix
By fixing this issue, we eliminate less code, and there is potential for improving our app's performance and marginally decreasing our app's size.
Some solutions to fixing this issue.
Delete the Nutrients class and replace it with a HashMap. We know that all of the material is going to be in there.
Description and Issue
The problem with the current database existing right now is that it is being improperly implemented. Some cases include: No singleton type pattern, bad use of HashMaps, and an overall bad design for the bridge-cross way between API and DB.
The Fix
By fixing this issue, we eliminate less code, and there is potential for improving our app's performance and marginally decreasing our app's size.
Some solutions to fixing this issue.
Delete the Nutrients class and replace it with a HashMap. We know that all of the material is going to be in there.