On Jun 29, 2007, at 2:54 PM, Florent THIERY wrote:
I am considering using Amazon EC2 as flv media streaming platform.
This sounds fun.
Due
to the current lack of dynamic network balancing (automated server
instanciation / destruction) , we have to rely on custom solutions.
Candidates are:
- webserver (httpd) cluster with custom pound as redirector/load
balancer + glue
- rtmp-based solutions (+dns round robin) + glue
Another option is HTTP redirect based load balancing. You could have
Web servers (possibly outside EC2, since EC2 isn't good for Web
servers) simply redirect all FLV or RTMP requests to the least-loaded
streaming server.
And for deploying them on Amazon EC2, the complexity of images has to
remain very easy, especially for the bootstrap phase. That's exactly
what p2p apps sometimes offer: automatic joining.
It sounds like you want a cluster membership protocol. This doesn't
necessarily have to be P2P; if you're going to have a central Web
server or load balancer anyway, then all the other servers can just
send heartbeats to the central master. The master can also start/stop
instances.
I would be glad to get pointers towards p2p-oriented http distributed
caching (such as dijjer) or media serving (like fluemotion),
scalability, load balancing considerations and hopefully feedback.
A random idea: To save on S3 traffic, you could use a memcached
cluster as a cache.
Wes Felter - [EMAIL PROTECTED] - http://felter.org/wesley/
_______________________________________________
p2p-hackers mailing list
[email protected]
http://lists.zooko.com/mailman/listinfo/p2p-hackers
