The "cloud provider rates" for this are a bit crazy. It's great bunny.net is offering a (more flexible!) product basically for free.
The NTP Pool does ~1m dns queries a second on the hourly peak with a small-ish (old) Go program (called `geodns`) running on a bunch of mostly small VMs around the world. The average is much less, but paying $0.70/million for ~11 billion queries a day would be a lot of money for a "random volunteers on the internet" project at "cloud provider rates".
Bunny's scriptable DNS is something I geek out so hard over. Bunny's DNS products in general, actually, are highly underrated. Kevin, my offer still stands to come work on it! :P
I actually went and looked at the linked Terraform blog post and I realized something.
It mentions that you used CDKTF because you prefer its expressiveness. The actual TF is generated from CDKTF. Having struggled with understanding and writing TF in the past, now, I don't really have to care with agents. I let them rip, then just read the plan output.
I am sure we will find more such examples where we can rip out an intermediate step completely because of agents.
Yes, same experience here. Was also a breeze to go from CDKTF TypeScript to TF HCL and shed a substantial number of dependencies as a result. Very happy with where it's at today, but also happy I came in through CDKTF.
Hasn't stuff like this been solved with anycast and typical routing algorithms of old etc? Or is this solving a different problem? (This doesn't affect me but have been considering moving some stuff from aws/cloudflare to bunny)
Very few providers offer anycast. It's also kind of simpler to take servers from multiple providers and have DNS be the integration layer between all of those.
Some hobbyists do anycast on their own, but this is more complex. See https://tylerobrien.dev/posts/2022/06/28/building-an-anycast... for example. This also require some advanced traffic engineering: what looks close for BGP may be on the other side of the planet. Relying on DNS only is more accessible.
The "cloud provider rates" for this are a bit crazy. It's great bunny.net is offering a (more flexible!) product basically for free.
The NTP Pool does ~1m dns queries a second on the hourly peak with a small-ish (old) Go program (called `geodns`) running on a bunch of mostly small VMs around the world. The average is much less, but paying $0.70/million for ~11 billion queries a day would be a lot of money for a "random volunteers on the internet" project at "cloud provider rates".
Bunny's scriptable DNS is something I geek out so hard over. Bunny's DNS products in general, actually, are highly underrated. Kevin, my offer still stands to come work on it! :P
I actually went and looked at the linked Terraform blog post and I realized something.
It mentions that you used CDKTF because you prefer its expressiveness. The actual TF is generated from CDKTF. Having struggled with understanding and writing TF in the past, now, I don't really have to care with agents. I let them rip, then just read the plan output.
I am sure we will find more such examples where we can rip out an intermediate step completely because of agents.
btw CDKTF was deprecated on December, 2025.
I liked it but, it was a hassle to get it running.
Yes, same experience here. Was also a breeze to go from CDKTF TypeScript to TF HCL and shed a substantial number of dependencies as a result. Very happy with where it's at today, but also happy I came in through CDKTF.
There is a community fork: CDK Terrain (https://cdktn.io/).
Hasn't stuff like this been solved with anycast and typical routing algorithms of old etc? Or is this solving a different problem? (This doesn't affect me but have been considering moving some stuff from aws/cloudflare to bunny)
Very few providers offer anycast. It's also kind of simpler to take servers from multiple providers and have DNS be the integration layer between all of those.
Some hobbyists do anycast on their own, but this is more complex. See https://tylerobrien.dev/posts/2022/06/28/building-an-anycast... for example. This also require some advanced traffic engineering: what looks close for BGP may be on the other side of the planet. Relying on DNS only is more accessible.
> I run seven small NixOS virtual machines to host this blog around the world
Wow!
Vincent, I love your map design on the blog post!
Thanks. I spent a non-trivial time just on the little animations!
Both the animations and the content made it one of my favorite posts of the week. Hope you don't mind me sharing for you.