The article is about running your own DNS server, which is, and must, always be available to everyone. What you are talking about is running a DNS resolver, but that is not the topic.
It's both, and more, in a way. But it's primarily a DNS tweaking tool, and does not support things like zone transfers. Which you usually don't need with a small-scale personal setup anyway.
Async fixes one problem with microservices. It does not fix the unexpected latency swings, the network timeouts and errors, the service disruptions when the microservice is unavailable, etc.
or the mismatch between request and response when using HTTP, or the overhead of using RPCs to protect against the previous scenario, or the issue of updating one microservice and not updating all the dependents
A separated component does not necessarily mean a microservice. It could be its own process, its own module, or even just its own function, which is fine. But microservices bring their own problems.
Theoretically, if solar did not make much economic sense at all, it would be purely a signalling thing. And those kind of things do spread by the ”catching on” effect. People might then get solar panels just to be seen as the kind of people who have solar panels, i.e. not the wrong kind of people.
I genuinely believe there's an xkcd for everything. I was only reading about the creator, Randall Munroe a few days ago and he's clearly very talented.
reply