title: Firestore - Saving Money on Document Reads
body: <p>I have a collection of 5,000 Artists from Firestore that I would like to load into my application as a searchable dropdown. The cost of doing this per user every page load is pricey. I have 10,000 active users a month.</p>
  <p>I tried Algolia, but the number of users on the site makes it a very pricey option. And loading 5,000 records every page load adds up quickly with Firestore. My thought is to store the names and IDs of all of the artists in a single document array in Firestore so that the cost is only 1 per page load as opposed to 5,000. Then, load additional data when an Artist is selected.</p>
  <pre><code>artists = {
    uniqueId: 'Artist Name',
    uniqueId2: 'Second Artist Name',
  }
  </code></pre>
  <p>I expect to save hundreds of thousands of document reads a day with this method. The only added annoyance is doing things client-side. But, this isn't too much trouble. I was hoping to gain insight into what others were doing. Should I consider storing some data in MySQL?</p>