The issue of network latency and loss – and how we meet the challenge of developing cloud-ready applications on best-effort networks – is a topic that has gained a bit more exposure recently with the Alcatel and Cisco announcements, coinciding with a paper from Joe Weinman.
In addition to the demands of realtime cloud applications, another reason that the network is returning to the foreground of discussion is IPv4 exhaustion. I’ve spent a fair amount of time looking at this particular issue in 2011, including the likely impact, in terms of costs and performance, of the various duct-tape IPv6 transition methods that are going to be implemented globally. Here is a copy of the slides from my presentation’ at Cloudcamp London (5th October 2011).
The internet has become our defacto distribution network for utility computing (otherwise known as cloud computing). The global response to IPv4 exhaustion has, unsurprisingly, not been timely adoption of IPv6; as such we now face an immediate future internet where the incumbent players dictate the terms and conditions for entry. This is likely to have a negative impact on innovation in systems that are built on cloud.