This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Hitesh Kumar Pithadiya wrote:I need a suggestion on the Architecture Part of a high traffic Web Site in Java as we are planning to build a system on the Web hit by approx. 1 Million users a day.
Like Campbell, I'm not exactly sure what architectures there are - the goalposts keep changing - but any of the ones you listed (including JPA/Hibernate) would probably do the job.
What you will need to do though is come up with much better metrics than you've given us. '1 million users a day' is of very little use:
How many database transactions/sec does that equate to?
How many HTTP requests/sec?
How many actual users (ie, accounts) do you have?
How long does the average user stay "logged on"?
What sort of growth do you expect over the next 1/5/10 years?
(and I've probably missed out a lot)
There are also a pile of non-Java technologies like clustering, distributed db's or caching servers that might help; or indeed, simply throwing more hardware or a bigger network pipeline at the problem; but until you can come up with some accurate concrete figures you're kind of whistling in the wind.
Isn't it funny how there's always time and money enough to do it WRONG?
Articles by Winston can be found here
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com
subject: High Traffic WebSite Architecture Suggestion