Topics
-set user expectations
-what system does vs what you tell the user
-ordering problem
-queued writes
-you need queued reads, otherwise things are out of order
reddit & digg use asnc patterns
msdn forums is sync
-considering using async
-how do you handle a post (does the user expect their message to show up right away)?
-users expect their message to show up right away
-they may double post the message, thinking it was lost
many sites use distibuted cache to handle load, still have simplicty of sync programming
async pros and cons
-cosistent reponse times
-does not help with performance or efficiency
-does make it easier to scale
-increases total resource usage
how do you handle failed writes?
-remove the data from the cache on failure
example: spam checking
-done in the background
-could be done before the write to avoid ever persisting the spam
tools
-msmq
-sql service broker
-rabbit mq
-active mq
-nservice bus
-mass transit
batching can help improve effeciency with async writes
Comments (0)
You don't have permission to comment on this page.