Scaling our data utility

we've built out this country codes directory, it's a solid data utility, but we're starting to see some real headaches with how we manage and serve the data. specifically, when it comes to querying and keeping everything snappy for users. i'm talking about things like concurrent requests for various country codes, especially with the geo-ip lookup stuff we're trying to integrate. the database is getting hammered, our postgresql instance is really struggling under the load of these high-volume lookups as usage and traffic increase. we're looking at ways to re-architect our data layer for maximum efficiency, needing to optimize for extreme query efficiency and scalability when dealing with frequently accessed, but largely static, international reference data like country, dialing, and ISO codes. so, what advanced database indexing strategies, caching layers (beyond standard redis, maybe something more specialized for this type of data?), or architectural patterns would best handle high-volume, real-time lookups for this kind of data utility without compromising performance or future expansion? we're really at a crossroads here, the current setup just aint cutting it. help a brother out please...