On Thursday 25 October 2007 07:19, Dossy Shiobara wrote: > On 2007.10.25, Jay Rohr <[EMAIL PROTECTED]> wrote: > > In general, I would not recommend using sob. It was developed for very > > specific requirements at AOL and it does not scale well under load - > > volume or frequency. We are in the process of replacing it with > > something else. > > Okay, this is just plain misinformation. SOB works very well for what > it was intended for, a low-write, high-read, distributed service for > small objects (thus, the name "SOB").
I would agree with this. Although I haven't used SOB, I have looked at the code. If anyone can improve upon reading static information from disk or memory, then they can outperform SOB. My understanding is that SOB simply 'compiles' dynamic information into a semi-static form. For instance, how often does the weather change in Seattle? Although the information is dynamic over large timescales, over the course of one day, not much changes. If you have 100 queries a second for Seattle weather, maybe put it into a SOB and let a backend service update it when needed. Just because you have dynamic data doesn't mean you have to shoot yourself in the foot when your service becomes popular. I wrote a small subscribe/push service that for some reason I called a tclbean. (I gave up waiting for NVs to be released by AOL). Essentially a server (as client) connects to the publisher and gives a callback address and a series of nsv arrays to subscribe to. The publish server connects back to the client. A scheduled proc on the publish server pushes updates. The original client can then always grab information from the nsv array and not worry about anything else. It is hard to imagine scalability problems with design, and I doubt there are any with SOB. But it would be interesting to hear what issues were found. tom jackson -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
