You're developing a customer loyalty app for a small chain of retail stores. The app will need a backend database to maintain custom While designing the app, you're conducting a planning meeting with your client to determine the scope of the project and resolve que about the project.

Client:

I$\text{'}$m trying to understand how all this will work$-$how the app and the database will work together. Where will you get the information database?

You:

This data is specific to your company, so it's called data. Your customers will enter their personal information when they accounts. Then sales transactions will continue to add data about each customer over time.

You're developing a customer loyalty app for a small chain of retail stores. The app will need a backend database to maintain custom While designing the app, you're conducting a planning meeting with your client to determine the scope of the project and resolve qu about the project.

$2.$ Client:

That sounds like a lot of data. Won't the database get too big to find information quickly?

You:

Good question. We can build in a$($n$)$ Jor two to help speed up queries. It will take up a bit more space, but will greatly efficiency for user interactions.