myfaces-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From José Luis Cetina <maxtorz...@gmail.com>
Subject Re: [OT but still JSF]: Clustering, session replication, and database, too
Date Mon, 21 Oct 2013 01:03:59 GMT
El 20/10/2013 19:34, "Howard W. Smith, Jr." <smithh032772@gmail.com>
escribió:
>
> so, db server is on a separate machine/server on the network, and each EAR
> is referencing the (one) db server via IP address?
>

Yes 2 tomee instances each in separete server point to a third server that
only serve as db server. Thats why y have clustering only in webapps and
not in db.

> also, do you have an embedded db server (running inside of tomee and using
> tomcat jdbc pooling) or network db server/engine?
>
>

I use tomcat jdbc pooling (tomee with defined connections in tomee.xml)

> On Sun, Oct 20, 2013 at 5:32 PM, José Luis Cetina <maxtorzito@gmail.com
>wrote:
>
> > Ear with all my apps in each server (2 server each with their own ear)
then
> > each server insert/read in another unique db server.
> > El 20/10/2013 16:09, "Howard W. Smith, Jr." <smithh032772@gmail.com>
> > escribió:
> >
> > > Hmmm, i thought you said that you have EAR on one server and database
on
> > > separate server. are you running 2 tomee on same server; one tomee =
EAR,
> > > another tomee = database?
> > >
> > >
> > >
> > > On Sun, Oct 20, 2013 at 11:52 AM, José Luis Cetina <
maxtorzito@gmail.com
> > > >wrote:
> > >
> > > > By the way im not using remote calls. All my apps are in the same
ear
> > > with
> > > > this i can inject my ejb local interface for calling methods in ejb.
> > > > El 20/10/2013 07:49, "Howard W. Smith, Jr." <smithh032772@gmail.com>
> > > > escribió:
> > > >
> > > > > just remembered-and-revised 2nd question, below...
> > > > >
> > > > > On Sun, Oct 20, 2013 at 8:35 AM, Howard W. Smith, Jr. <
> > > > > smithh032772@gmail.com> wrote:
> > > > >
> > > > > >
> > > > > > On Sun, Oct 20, 2013 at 8:17 AM, Mark Struberg <
struberg@yahoo.de>
> > > > > wrote:
> > > > > >
> > > > > >> This can also be very helpful to 'scale out' in case you
need
> > > > > performance:
> > > > > >>
> > > > > >> All write stuff is only performed on the master node, but
> > expensive
> > > > > >> queries/searches might be performed on the n replication
nodes. Of
> > > > > course
> > > > > >> this needs a special handling in your app, but allows to
move
the
> > > > > expensive
> > > > > >> queries away from your primary node.
> > > > > >>
> > > > > >
> > > > > > hmmm, had a question or two, or seeking clarification (or a
bit
> > more
> > > > > > details or even a reference to a blog/article/document).
> > > > > >
> > > > > > 1. scale-out usually mean different physical servers? scaling
out
> > > > > multiple
> > > > > > databases on one physical server, usually (or I would assume)
means
> > > > that
> > > > > > the hard drive becomes the bottleneck, if hard drive contain
> > multiple
> > > > > > databases. right?
> > > > > >
> > > > > > 2. this needs special handling in your app? can you please
clarify?
> > > > > >
> > > > > >
> > > > > thanks!
> > > > >
> > > >
> > >
> >

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message