So I came across this blog post about DNS (Domain Name Service) over HTTPS (HyperText Transfer Protocol-Secure) [1] and …
… yeah …
… I feel that this is it. The Internet has ossified. There are no new programs or protocols—it's either on the web, or it doesn't exist.
Last week it came down from On High™ that both “Project: Wolowizard [2]” and “Project: Sippy-Cup [3]” will be making REST (Representational State Transfer) [4] calls, most likely over TLS (Transport Layer Security), rather than the current method of DNS (on a private network).
Because … reasons.
The company we query for data has drunk the REST (REpresentational State Transfer)/HTTPS über alles Kool-Aid™ and we get to suffer. We now get to make expensive network queries during the establishment of a phone call. We've been told not to worry, some load testing will be done, but hey, it's all good. It'll be HTTP (HyperText Transfer Protocol)/1.1.
For now.
Maybe HTTP/2.0 (which is nothing more than TCP (Transmission Control Protocol) over TCP over TLS if Google has their way, and it appears they are). But definitely HTTP/1.1 for now.
Oh, and the data we'll get back is in JSON (JavaScript Object Notation) [5].
Of course it is.
Lovely.
Damn hipster developers! Get off my lawn!
[1] http://bitsup.blogspot.com/2018/05/the-benefits-of-https-for-dns.html
[4] https://en.wikipedia.org/wiki/Representational_state_transfer