The ABC app shows its users information in "near-realtime". This information changes continuously from the backend. Users do not have access to write, just read. Each time the app goes up, it makes a request to the server, the server in turn makes multiple requests to the database, then transforms the data and returns it to the user. As the use of the app increases, the database begins to show "performance" problems. How do you suggest these problems are corrected without vertically scaling the capacity of the database? Remember that users only have access to read.