Given that it ultimately pokes around with Amazon's route53 infrastructure I'm not too sure that there'd be a gain if the site/processor were available in-house.
Even if the manipulation were local, the Amazon API would be remote, and not within a company's control.
Interesting idea though. Most of the backend is portable perl and easy to pull out..
Even if the manipulation were local, the Amazon API would be remote, and not within a company's control.
Interesting idea though. Most of the backend is portable perl and easy to pull out..