File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
http://aspose.com/file-tools
The moose likes Java in General and the fly likes High Traffic WebSite Architecture Suggestion Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Java » Java in General
Bookmark "High Traffic WebSite Architecture Suggestion" Watch "High Traffic WebSite Architecture Suggestion" New topic
Author

High Traffic WebSite Architecture Suggestion

Hitesh Kumar C
Ranch Hand

Joined: Sep 12, 2008
Posts: 35

Hi Guys,

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.

We already have that System as a Windows Based Application as we are planning to migrate the same to the web.

Being a Senior Engineer, i got this responsibility to look after the Architecture flow of the Application.

I need a Good UI Representation and Fast Database calls and i can't wait the User more then 3-4 seconds for a request.

I Decided to go for Front-end(JSF, JQuery, Ajax) and back-end as Oracle.

Would it be physable add a Persistent Layer as Well (JPA, Hibernate)?

Any comments and suggestions are greatly appreciated.

Kindly suggest.

OCJP 6.0, OCPJWCD 5
Hitesh Kumar C
Ranch Hand

Joined: Sep 12, 2008
Posts: 35

Any comments?
Campbell Ritchie
Sheriff

Joined: Oct 13, 2005
Posts: 40061
    
  28
Please read this.
Don’t know myself, but I do know that question is too difficult for this location, so I shall move it (probably to the wrong place, so it might move again).
Winston Gutkowski
Bartender

Joined: Mar 17, 2011
Posts: 8427
    
  23

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.

    Winston


    Isn't it funny how there's always time and money enough to do it WRONG?
    Articles by Winston can be found here
     
    I agree. Here's the link: http://aspose.com/file-tools
     
    subject: High Traffic WebSite Architecture Suggestion