> > Havingseveral instances of TomEE will create several persistence contexts > and lose transactional value, I assume.
Am I right here? I will look for solutions and let you know if I find a good one. Right now I am reading this: http://www.theserverside.com/news/1364410/Under-the-Hood-of-J2EE-Clustering (pasting here so that others having the same concerns can read :-) ). On Thu, Feb 23, 2012 at 6:50 PM, Romain Manni-Bucau <[email protected]>wrote: > Personally i think a good httpd configured as load balancer can be enough > for your need regarding TomEE. > > In all case you'll need something to organize the deployement and here > finagle can be good (camel too ;)). > > - Romain > > > 2012/2/23 Ravindranath Akila <[email protected]> > > > Hey, thanks for the quick response Romain. > > > > We are a social network. We will hit performance issues in three levels. > > > > 1. Our UI renderers will need increased memory over time and during > spikes. > > 2. The EJB layer, which is in place purely for transactional purpose > might > > need expansion in memory(that is were I would like your advice). > > 3. Our database might fail to offer fast enough read writes and might > give > > issues with locks. > > > > Hazelcast is a very good candidate for our UI renderes because we can > cache > > wall entries and other profile data easily. This will also reduce a lot > of > > load on the database. We will definitely have to figure out a way to > > partition the database and cluster it soon. > > > > On the other hand, I am not sure how to go about the requirements of > TomEE. > > Suppose we have some millions of users using the website, I am worried we > > will have to cluster TomEE to support the load (CPU and Memory). Having > > several instances of TomEE will create several persistence contexts and > > lose transactional value, I assume. > > > > Well, I am new to all this. But within a month I will have to figure out > > the best approach to scale as a social network. Right now, I have > narrowed > > down my options to choosing some of: > > > > 1. Using Hazelcast for caching data (Purpose: to increase performance and > > reduce load on database). > > 2. Using Finagle, and I have no idea how to do that. > > 3. Using JBoss or Glassfish with their clustering support. > > > > > > Any suggestions on how to scale TomEE is really appreciated! > > > > > > On Thu, Feb 23, 2012 at 6:08 PM, Romain Manni-Bucau > > <[email protected]>wrote: > > > > > TomEE supports failover and you can inject a remote ejb into another > > server > > > using the failover. > > > > > > We currently don't provide a "supervisor" node to control a cluster but > > > everything is here to control remote instances easily (for instance > > > deploying an app from a nexus). > > > > > > I guess you can do it easily starting hazelcast in each instance. > > > > > > Can you give more information on what you expect exactly (clustering > can > > > mean a lot of thing and i'm not sure to get your exact need)? > > > > > > I'm currently not aware of any plan but if the need is clear we could > do > > it > > > ;) > > > > > > - Romain > > > > > > > > > 2012/2/23 Ravindranath Akila <[email protected]> > > > > > > > Do we have support for clustering in TomEE? Are there plans for this? > > > > > > > > I found a discussion on Hazelcast here : > > > > > > > > > > > > > > http://openejb.979440.n4.nabble.com/Clustering-OpenEJB-with-Hazelcast-td2278415.html > > > > and > > > > this is all I can find with something close to clustering with TomEE. > > > > > > > > R. A. > > > > > > > > On Wed, Feb 22, 2012 at 1:59 PM, Ravindranath Akila < > > > > [email protected]> wrote: > > > > > > > > > Thanks a lot Romain. I will have a look at it. > > > > > > > > > > R. A. > > > > > On Feb 22, 2012 11:43 AM, "Romain Manni-Bucau" < > > [email protected]> > > > > > wrote: > > > > > > > > > >> Hi, > > > > >> > > > > >> It is mainly a deployment question. > > > > >> > > > > >> One way is to use the brandly new httpd server with its built in > > > dynamic > > > > >> load balancing feature to hit several dynamic instances of TomEE. > > > > >> > > > > >> Then of course your application should support to be distributed. > > > > >> > > > > >> - Romain > > > > >> > > > > >> Le 22 févr. 2012 06:55, "Ravindranath Akila" < > > > > [email protected] > > > > >> > > > > > >> a écrit : > > > > >> > > > > >> > Guys, > > > > >> > I tried Google on this and somehow found nothing worthy of > > using. I > > > > am > > > > >> > trying to figure out how to easily scale my application running > > atop > > > > >> TomEE. > > > > >> > > > > > >> > Suppose I have just 100 concurrent users today and tomorrow I > > have > > > to > > > > >> > double it, is there a way I can do it with a new TomEE instance > > > > running > > > > >> on > > > > >> > a different machine? What I mean is, what do I do when I hit > > machine > > > > >> > spcific limits on the cloud like 16GB RAM?(Rackspace) > > > > >> > > > > > >> > On the other hand, is it worth to also have a look at solutions > > > like > > > > >> > Finagle or do you think I can scale with Core EJB using TomEE? > > > > >> > > > > > >> > Sorry that the question is a bit out of context. > > > > >> > > > > > >> > Thanks! > > > > >> > Ravindranath Akila... > > > > >> > > > > > >> > > > > > > > > > > > > > > > > > -- > > > > Cheers! > > > > Akila... > > > > > > > > > > > > > > > -- > > Cheers! > > Akila... > > > -- Cheers! Akila...
