Hello, I wrote a post in the weekend that intent to explain, in a better manner, my idea for GSoC.
Please feel free to comment about this. Best regards, 2009/3/19 Cesar D. Rodas <sad...@gmail.com>: > 2009/3/19 Rasmus Lerdorf <ras...@lerdorf.com>: >> Cesar D. Rodas wrote: >>> 2009/3/19 marius adrian popa <map...@gmail.com>: >>>> On Thu, Mar 19, 2009 at 9:30 AM, Cesar D. Rodas <sad...@gmail.com> wrote: >>>>> Hello Andrey, >>>>> >>>>> 2009/3/19 Andrey Hristov <p...@hristov.com>: >>>>>> http://www.vl-srm.net/ ? >>>>> I've already seen this, and it is pretty similar, but it designs it's >>>>> very complex IMHO (http://www.vl-srm.net/doc/figures/srm-design.png). >>>>> My design will be simple, pretty close to the memcached. Part of its >>>>> simplicity will be only the RPC/RFC functionality, you won't be able >>>>> to instance remote objects (as the banana class of SRM). >>>>> >>>>> My idea it's provide an easy way to scale, you should be able to take >>>>> an existent project, cut some functions, export into a worker, and >>>>> hook your app. to the worker(s), I'll also write a little function >>>>> that will connect to the master process and generate functions that >>>>> will wrapper as local function, so your code won't change but it would >>>>> be able to scale. >>>> RPC is quite dead >>>> http://taint.org/2009/03/18/151218a.html >>> I can't figure out a better way to scale, of course this solution >>> wouldn't be for every page, but figure out the problem that great >>> sites such as yahoo, digg, wikipedia, wordpress and others faced to >>> scale. The RPC IMHO is a fast/cheap way to handle huge traffic. >> >> And I can tell you that we don't do this at all. Write your code such > I just said Yahoo as an example. > >> that it scales horizontally easily and throw lots of frontend servers >> with a low number of concurrent connections at it and you end up with a >> fast scalable site. You will obviously need to hit some central data > It would be almost the same, you will have dozens of front-end > servers that will have the necessary PHP code, but you would be able > to queue work or execute a remote function that is coded in PHP (so > you have PHP on both sides). The result could be stored using APC or > Memcached (IHMO APC is the best solution) to reduce the network > latency. > > I got the idea to code such a thing when I was at the Network > programming class, and the teacher explained SOA, it would be the > same. It is only an idea for GSoC, btw I will do it for my final work > at University and I will share the code, probably it can be useful to > someone. > >> stores, so there will be some network latency, but with local shared >> memory caching, you can avoid it on many requests. Taking a network hit >> for code execution doesn't make sense to me. >> >> -Rasmus >> > > > > -- > Cesar D. Rodas > http://cesar.la/ > Phone: +595-961-974165 > Rita Rudner - "Before I met my husband, I'd never fallen in love. I'd > stepped in it a few times." > -- Cesar D. Rodas http://cesar.la/ Phone: +595-961-974165 Robert Benchley - "I have tried to know absolutely nothing about a great many things, and I have succeeded fair... -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
