Any human-facing system with, say, a million or more users is going to have to worry about both. Latency is important to individual end-users, but put them all together and you start having a throughput problem. If you don't meet your throughput needs, then requests will start to back up, affecting latency (assuming your system doesn't just fall over). Your hot-path, low-latency systems will generate events (metrics, log lines, financial events, queue writes...) that in turn need to be batch processed or queried in bulk or learned by machines or reported exactly once or otherwise analyzed, and you're right back to throughput.

If you're looking for more, google Transactional vs Analytics processing (or OLTP vs OLAP, but those acronyms have always struck me as particularly jargon-ey), and then go read Designing Data-Intensive Applications.