Geek asks and answers

Choosing Java Spring as a scalable server platform for a large website

I am currently facing a dilemma regarding the appropriate server structure.

Basically, I want to choose the best structure for creating a large website in order to serve millions of page views. The website itself will have a large database and ajax reliant, and therefore, scalability will need to be planned from the very beginning.

My needs / requirements for a suitable server-side structure are as follows:

  • High-level OO language support with support for some metaprograms.
  • Appropriate scalability and load balancing at the frame level.
  • MVC architecture.
  • Support for ORM or atleast Support for object level mapping.
  • Support for proper routing (URL Rewriting).

Finally, my question is that the Java Spring framework is a suitable candidate for working on a large website based on the needs and needs mentioned above? Should I stick with something like Django or Rails?

+3
source share
6 answers

Spring is a good foundation. However, it alone will not solve your scalability problems (and no other framework will).

To increase the load on the servers, you need to make sure that your servers are stateless or use load balancers with sticky sessions. To reduce the load on the database, you will need caches. No structure will solve it for you.

, , .

+10

.

  • Spring Framework ( MVC DI).
  • Hibernate Framework.
  • - memcache/Infinispan .
  • /db.
+2

- , , - Java EE. EE 6 - , JBoss AS 7 - EE 6 - , , . .

Java EE 6, , , : CDI , - JSF, JAX-RS - RESTful, JPA2 - , JMS- .. .. Sun/Oracle Java EE 6 tutorial, , , .

JBoss , - Eclipse Java EE .

+2

, , . Spring/Spring MVC - :

  • URL-
  • ORM
  • -
+1

Spring.

  • , ,
  • .
0

-: -Static , -: http://nginx.org/en/. - . - gzip- @- . - . - # . - (HTML, CSS, JS, html ..)

: -, , , .. - , . - NBIO (JBoss Wildfly, Netty, Tomcat 8 ..)

: - . -Denormalizing mainting , . (, , ..). - @ ACID NoSQL, Orient DB.

0

More articles:


All Articles