An alternative approach would be to call "await util.promisify(socket.connect)(8125, host)" so that subsequent calls to send don't need to name the destination (and the underlying runtime could call send instead of sendto). Perhaps the author needs the messages to be sent to a new host quickly when DNS records change, but the trade-off might be different depending on the use case, and perhaps some applications might prefer to periodically re-connect the socket to re-resolve DNS.
The cost of running Vuvuzela is dominated by bandwidth, and the paper used AWS prices to estimate the cost; purchasing IP transit directly would lead to about an order of magnitude reduction in costs (still non-trivial, of course).
Order of magnitude? 1Gbit on amazon costs 22k/month. Even an order of magnitude cheaper sounds pretty damn expensive, two orders of magnitude still isn't "cheap".
It's really easy to underestimate how big of a ripoff EC2 bandwidth pricing is.
1Gbit in Chattanooga, TN cost $350 a month. You gotta buy some servers and maybe a colocation fee. Way less than $22,000 a month. Actually, while I was looking that up, a recent press release says they're deploying 10Gbit to homes for $299 a month. Things may have improved on business side, too. :)
On the expensive end you'd be looking at around $600 for such at $NOT_AMAZON, and on the cheap end you'd get it for "free" because a plenty of hosts have excess bandwidth.
DO doesn't separately charge for BW or enforce any limitations AFAIK.
Based on my reading of the article, it says that OpenBSD always uses the same key, scr_key[0], and does not implement the use of different keys for different parts of the disk. I haven't looked at the OpenBSD source code to confirm this, though.
