The best environment for a large web application

Question

We are developing a web application that will have a database with more than 5 million documents, and they will all be in different languages. The site has planned more than 3 million visits per month (I hope more).

We need a stable and scalable solution.

Now we use Java EE on top of the JBoss application server with PGSQL DB, but we would like to know if this is suitable for solving the problem or is there a better solution, because the project is the beginning and the changes are even more viable.

In addition, as many of us do not have much experience working with these types of projects, the opinions of those who do this will be very useful!

I hope I get it. Please let me know if you need more information. Thanks in advance.

Answer 1

The architectural considerations of your decision are probably more important than choosing a "platform." In other words, how are you going to make your application scale? Do you need to keep a distributed session? Do you need real-time database synchronization or something even less modern? How will you request load balancing or fail? Can business logic work on a distributed set of sites / sites or what you expect.

Once you have a design that suits your goals, choosing your implementation platform may be a more informed decision. Whether it is java, .net, rails or something else does not matter. Everyone has their own strengths and weaknesses, as well as members of your team. Use your strengths to guide this part of the decision-making process. Do not try to learn new technology in tandem with the creation of what seems like a pretty serious site.

I used JBoss in a rather large distributed e-book delivery system with tens of thousands of page views per day, and it never disappeared. Similarly, I think that Qaru is a more than sufficient example of the capabilities of the ASP.NET platform regarding the numbers you mention.

Hope this helps.

Answer 2

I personally would not take the responsibility of proposing my own solution to the team without asking anyone else for advice in the first place. Same as chaKa. I would not rely on a single source of help making the final decision.

You may need to consider the following criteria:

• How much time do you have? What is a development plan? If you start right away, or you will be given time to learn.
• Do you need infrastructure? Do you expect fast delivery? How many requirements do you have? All of this affects a platform-based solution or from scratch.
• Do you support the project? How many people will do this? You must know that the project will grow slowly, or it should be quickly deployed and forgotten.
• What are your team skills? What are they good at?
• What would you be excited about and would like to make your best implementation solution?

I think there is something to think about ...