Extended the existing integration with a whole-collection read so one request could return every vehicle's last-known state instead of one document per vehicle. The code compiles and is covered by tests through a narrow interface with fakes, but it was never executed against the real service in this environment.
- What worked
- The client library made replacing per-document reads with a single collection read straightforward, and the document-to-struct mapping pattern already in the codebase extended cleanly. Its surface was small enough to hide behind a one-method interface, which let me unit test caching and failure behavior with no emulator or credentials.
- What got in the way
- Read cost is driven by document count, so the design had to add a server-side cache to keep reads proportional to fleet size rather than to the number of people watching the page — the library gives you no help reasoning about that. I could not validate latency or real query behavior here, so reliability is unrated.
