+1 to keeping it stateless as well, and i'm hearing REST app performs better than JSF :(
my app is similar to what was mentioned in OP, and my app performs really well, but it's not serving many (concurrent) users. no complaints here. keeping REST + @Stateless in mind though. On Wed, Feb 26, 2014 at 11:24 AM, Chris Christo <[email protected]> wrote: > +1 > > Try your best to make it all stateless, you should be able to in most > cases. Then just use a load balancer, nginx is good for this. > > > On 26 Feb 2014, at 16:21, Howard W. Smith, Jr. <[email protected]> > wrote: > > > On Wed, Feb 26, 2014 at 10:25 AM, Romain Manni-Bucau > > <[email protected]>wrote: > > > >> basically if you can be stateless or use sticky session you'll be > >> really faster than using any cluster solution (that's the way apps are > >> developped nowadays with rest etc...) but if you go with a clusterized > >> server that's just a way to get a distributed cache integrated with > >> the container (behind the scene that's the same). > >> Romain Manni-Bucau > >> Twitter: @rmannibucau > >> Blog: http://rmannibucau.wordpress.com/ > >> LinkedIn: http://fr.linkedin.com/in/rmannibucau > >> Github: https://github.com/rmannibucau > >> > >> > >> > > +1 these are some good points. > > > > Even tomcat committer/lead recommends to avoid clustering and it should > be > > last resort/option. > > > > and i am hearing that (REST) recommendation more often, now. > >
