WebLogic load balancing -
i'm developing project supported on weblogic clustered environment. i've set cluster, want load-balancing solution (currently, testing purposes, i'm using weblogic's httpclusterservlet
round-robin load-balancing). there documentation gives clear comparison (with pros , cons) of various ways of providing load-balancing weblogic?
these main topics want cover:
- performance (normal , on failover);
- what failures can detected , how fast failover recovery;
- transparency failure (e.g., ability automatically retry idempotent request);
- how each load-balancing solution adapted various topologies (n-tier, clustering)
thanks in advance help.
is there documentation gives clear comparison (with pros , cons) of various ways of providing load-balancing weblogic?
it's not clear kind of application building , kind of technologies involved. but...
you find useful information in failover , replication in cluster , load balancing in cluster (also @ cluster implementation procedures) but, no real comparison between different options, @ least not knowledge. but, choice isn't complex: 1. hardware load balancers perform better software load balancers , 2. if go software load balancers, weblogic plugin apache recommended (by bea) choice production. actually, web apps, pretty usual put static files on web server , use apache mod_wl plugin. see installing , configuring apache http server plug-in chapter.
these main topics want cover:
performance (normal , on failover): if question persistent session, weblogic uses in memory replication default , works pretty relatively low overhead.
what failures can detected , how fast failover recovery: unclear protocols you're using. see connection errors , clustering failover.
transparency failure (e.g., ability automatically retry idempotent request): clarifying protocols using make answering easier. if question http requests, see figure 3-1 connection failover.
how each load-balancing solution adapted various topologies (n-tier, clustering): question unclear , vague (for me). maybe have @ cluster architectures.
oh, way, nice chapter must read clustering best practices.
Comments
Post a Comment