Thanks for the great responses ... some more detailed parameters have to be drawn out:
1. I can't tolerate delays of more than a few milliseconds. 2. I can't lose events. 3. I can't tolerate duplicates (although there is some level of duplicate protection downstream, I can't rely on it). 4. The events are not very frequent, say one every 5-10 minutes. 5. memcache was an early thought but it introduces another failure point and another configuration item. Given the previous point (the events are not very frequent), a transactional database should be a sufficient replacement. -- You received this message because you are subscribed to the Silicon Beach Australia mailing list. Vist http://siliconbeachaustralia.org for more Forum rules 1) No lurkers! It is expected that you introduce yourself. 2) No jobs postings. You can use http://siliconbeachaustralia.org/jobs 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/silicon-beach-australia?hl=en?hl=en
