How the performance is being affected when calling multiple collections to fill relationships in firestore

Question

I obtained a firestore database with 2 collections of patients and appointments and I am trying to make a query to fill an appointment table in an html view that also contains patient information, however, since firestore does not handle the union between documents, I don't know how it could affect performance if for each appointment document, call the patient's collection and, therefore, get the related data.

Is the Firestore API smart enough to join all those queries and make a single HTTP request?

I am currently using Java with the Firestore administration API to perform queries.

score 1 · Accepted Answer · answered Jan 27 '20 at 15:23

The Firestore clients use HTTP2 to communicate with the server when possible. The requests will be pipelined over a single connection in that case.

Alternatively, consider duplicating the minimal data for each patient into their appointment documents. This type of data duplication is quite common in NoSQL databases, and is a typical trade-off of write performance/code cost vs read performance.

Also see:

Google Firestore - how to get document by multiple ids in one round trip?
the Get to know Cloud Firestore video series

Thats pretty much I wanted to read!, also I will take your advice to segregate some data into the appointment documents — Jorge L. Morla, Jan 27 '20 at 15:40

How the performance is being affected when calling multiple collections to fill relationships in firestore

1 Answers1