Mostly faangs use load balancers and don't return more than one A/AAAA record. Sometimes there's some CNAME chaining which isn't ideal, but might be expedient. Otherwise, not too much to optimize.
Otoh, they like their really short TTLs, which results in a lot of queries.
Yeah, that's the idea, but then there's stuff like this:
forums.adobe.com. 5 IN CNAME forum-redirects.trafficmanager.net.
forum-redirects.trafficmanager.net. 60 IN CNAME encoderfuncus.azurewebsites.net.
encoderfuncus.azurewebsites.net. 30 IN CNAME waws-prod-mwh-007.sip.azurewebsites.windows.net.
waws-prod-mwh-007.sip.azurewebsites.windows.net. 1800 IN CNAME waws-prod-mwh-007.cloudapp.net.
waws-prod-mwh-007.cloudapp.net. 60 IN A 52.175.254.10
On a totally cold lookup, that takes at least 13 queries to load, because of the long CNAME chain, and azurewebsites.windows.net is sub-delegated with NS (with 5 minute ttl). That's a lot of back and forth to chase, and then much of it needs to be redone if someone comes back soon.
Otoh, they like their really short TTLs, which results in a lot of queries.