I've been experimenting with using a CDN to cache QRZ XML lookups so that I can avoid storing callsign data in a database not worry about refreshing stale contact info perform real-time lookups during peak traffic time avoid writing separate code and logic for qrz lookups and local db lookups optional: get JSON formatted data instead of XML If you're interested in testing the service to explore possible use cases here are a couple endpoints: XML Format same as normal QRZ XML just prepend the url with http://35.201.90.13/?url= example: http://35.201.90.13/?url=https://xmldata.qrz.com/xml/current/?s=YOUR_SESSION_KEY;callsign=AF7TI JSON Format same as normal QRZ XML just prepend the url with http://34.117.252.26/?url= example: http://34.117.252.26/?url=https://xmldata.qrz.com/xml/current/?s=YOUR_SESSION_KEY;callsign=AF7TI If you find the service useful and want to use it for production workloads with an SLA let me know. 73s, Matt
