This article has the right title and discusses the idea of services, not servers, but misses an even bigger opportunity to discuss how you can legitimately ditch lots and lots of servers. WebRTC means that every application can have aspects of peering and reduce the need for centralization in servers.
Back in 2010, well before WebRTC, I posted the following use case on the WHAT-WG mailing list that explores using peering to offset CDN static asset serving costs in social games. It was a while ago when I was a product manager and a lot less technical, so excuse some of the naive misconceptions I may have made at the time.
http://lists.w3.org/Archives/Public/public-whatwg-archive/20...
Anyone interested in exploring an idea like iron.io, but in their own application stack should check out the following projects from James Halliday (substack)
It'd be awesome to see someone combine WebRTC with the basic idea behind Seaports to allow semantic versioning of services provided by your application's users.
Back in 2010, well before WebRTC, I posted the following use case on the WHAT-WG mailing list that explores using peering to offset CDN static asset serving costs in social games. It was a while ago when I was a product manager and a lot less technical, so excuse some of the naive misconceptions I may have made at the time. http://lists.w3.org/Archives/Public/public-whatwg-archive/20...
Anyone interested in exploring an idea like iron.io, but in their own application stack should check out the following projects from James Halliday (substack)
https://github.com/substack/seaport
https://github.com/substack/airport
https://github.com/substack/fleet
https://github.com/substack/airport-cluster-example
It'd be awesome to see someone combine WebRTC with the basic idea behind Seaports to allow semantic versioning of services provided by your application's users.