Not sure if you're looking for something that is implemented in CF/Java, but...
I am a huge fan of backgrounding as much as possible and my first tool of choice is Beanstalkd. http://kr.github.com/beanstalkd/ It has a very simple text based protocol (think memcached). It allows you to set deadlines on jobs and to bury jobs for future review. It supports job prioritization and delayed starts. It is also very very fast. There is a Java client - probably not too hard to wrap it in a CFC. I love me some Beanstalkd. /Cody On Mon, Aug 16, 2010 at 6:41 PM, Marc Esher <[email protected]> wrote: > Hi all, > Since it's been so long that cfcdev has had a message, I know you'll > all put down the beers, put the spouses and kids to bed, and jump at > the chance to pitch in here. > > I'm whipping up a prototype app -- not for work, not for homework -- > that I'm thought-experimenting about "how would I run this in a > multi-server environment?". I'm not looking for code samples or > anything really specific, just options. > > Imagine you have a *lot* of background work to do. You have an unknown > -- and potentially elastic -- set of servers with which to do the > work. It's probably easiest to think of it as if you were running this > thing on Amazon EC2 or another service. You have a "queue" of work to > be done. You have worker servers to do the work. > > What are your options for scheduling that work with ColdFusion? In an > ideal world, there'd be a shared queue, and workers would "take()" off > of that queue, with zero contention... i.e. as soon as one server > takes off the queue, that task is immediately unavailable to another > server that also attempted to take it. > > I'd normally use java for this, but I want to use CF to see how badass > it can get in a situation such as this one. And this means no java > Timers, TimerTasks, or my dear friends the ExecutorService and its > wonderful relations... straight CF. I'm not opposed to event gateways, > though I'd really like to stay away from a JMS server if I can help > it. Importantly, it needs to be fairly easy to debug, which is > always a problem in cases such as these. > > Thoughts? > > Oh, I know: this is like when the boss comes in and says "we need it > fast, we need it simple, and we need it now". I have a good idea of > how I'd do this with java, but I'm mostly interested in what CF could > provide. > > Thanks! > > Marc > > -- > You received this message because you are subscribed to the Google Groups > "CFCDev" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/cfcdev?hl=en. > > -- You received this message because you are subscribed to the Google Groups "CFCDev" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/cfcdev?hl=en.
