Future of Web Apps (FOWA)
Session: Dopplr: It's made of messages
Note by Phil Wilson:
make "small pieces loosely joined" part of your application. Make it small pieces which talk to each other. The & of Unix is its best benefits. Do things in the background.
matt's omnigraffle slide - all these things happen independently of an HTTP request - queued background tasks and inputs from other locations on the network
the talks so far seem to have been questioning the classic big iron solutions in terms of big hardware and big powerful databases.
book: john osbar, capacity planning
http://www.amazon.co.uk/Art-Capacity-Planning-Scaling-Resources/dp/0596518579/ref=sr_1_1?ie=UTF8&s=books&qid=1223552503&sr=8-1
book: enterprise integration patterns, Gregor Hohpe, Bobby Woolf et al.
http://www.amazon.co.uk/Enterprise-Integration-Patterns-Designing-Deploying/dp/0321200683/ref=sr_1_1?ie=UTF8&s=books&qid=1223552480&sr=8-1
Message queues in Dopple are pieces of JSON.
The news of messaging and queueing has been getting a lot of traction in what i've been reading over the last 6 months. quotes from les orchard.
eventual consistency is what's important - it doesn't need to be permanently consistent - local consistency is all that's important - the view of one user onto an application.
Joe Gregorio, bitworking.org/news/218/N-1
separate queues and processes is a nice way of splitting out logs, and attaching to the queues and effectively tail -f ing them.
damn, i really am gong to have to read rabbitmq and activemq. have been trying to avoid it! two main protocols, stomp and AMPQ
matt's omnigraffle slide - all these things happen independently of an HTTP request - queued background tasks and inputs from other locations on the network
the talks so far seem to have been questioning the classic big iron solutions in terms of big hardware and big powerful databases.
book: john osbar, capacity planning
http://www.amazon.co.uk/Art-Capacity-Planning-Scaling-Resources/dp/0596518579/ref=sr_1_1?ie=UTF8&s=books&qid=1223552503&sr=8-1
book: enterprise integration patterns, Gregor Hohpe, Bobby Woolf et al.
http://www.amazon.co.uk/Enterprise-Integration-Patterns-Designing-Deploying/dp/0321200683/ref=sr_1_1?ie=UTF8&s=books&qid=1223552480&sr=8-1
Message queues in Dopple are pieces of JSON.
The news of messaging and queueing has been getting a lot of traction in what i've been reading over the last 6 months. quotes from les orchard.
eventual consistency is what's important - it doesn't need to be permanently consistent - local consistency is all that's important - the view of one user onto an application.
Joe Gregorio, bitworking.org/news/218/N-1
separate queues and processes is a nice way of splitting out logs, and attaching to the queues and effectively tail -f ing them.
damn, i really am gong to have to read rabbitmq and activemq. have been trying to avoid it! two main protocols, stomp and AMPQ
