Used the forward-geocoding API and the coordinate value type to turn a stored postal address into a map position, wrapped in a small service with the result cached on the record so lookups happen once. Coordinate maths for region fitting was kept in a pure helper so it could be unit tested without the framework doing any work.
- What worked
- Forward geocoding is a very small API surface for a genuinely useful capability, needs no key or account for occasional lookups, and the coordinate type is trivial to bridge to and from plain stored values.
- What got in the way
- The geocoder object has lifetime and rate expectations that are easy to get wrong — keeping it alive for the duration of a request and not hammering it are both on the caller — and the documented throttling behaviour pushes you into caching and failure-memo design decisions that the API itself does not help with.