Hi guys, I was wondering if you guys could educate me or at least point me to some useful resources.
Lets say I was tasked with architecting a web application where I was expecting huge volumes of transactions, circa millions of transactions in a small hour or so window at peak times. I could do a traditional n-tier architecture with the web at one end, business/service layer in the middle and a big database at the other end. Perhaps even do JMS between components (with Active MQ). Would that be up to the job? What if it wasn't. What are my choices? >From what I know, there are 2 options: 1. optimise for the single threaded model - something like what LMax has done (Martin Fowler has a post on his blog) and try and remove the DB from the loop. I (think) this also includes software transactional memory-type architectures? 2. explicitly move to a multi-threaded model. Is that roughly the options? What do Facebook and Twitter do to manage the huge load? All feedback welcome. Cheers R -- You received this message because you are subscribed to the Google Groups "The Java Posse" 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/javaposse?hl=en.
