This is probably going off the topic somewhat, but seeing how critical this
seems to be (replication etc) are you sure about using MySQL ? I understand
it doesn't support transactions (or didn't until recently). Are you happy
that you data integrity is assured ?
Jon.
On Wednesday 10 January 2001 15:36, Alistair Hopkins wrote:
> Has anybody written a failsafe/load balancing jdbc driver?
>
> It should be possible to have an implementation of a jdbc driver which is
> configured to load >1 other jdbc drivers with connections to >1 databases,
> and to call them in order of preference (or in rotation for load balancing)
> for selects and call to all of them for updates/insets/deletes/ddl. You
> would then have multiple db with synchronised data, even of different
> types.
>
> If one fell over, the driver would have to log the SQL statements to be
> executed. If one had a SQL exception, then the transaction on the others
> would have to be rolled back: i.e., writing would carry quite an overhead,
> and it would be very hard to do normal transaction processing.
>
> Also, when you say 100 concurrent users, do you mean concurrent human (they
> read the web page) or concurrent loadtester (ask for another as soon as
> they get the first). There's maybe an order of magnitude difference:
> anybody have any figures on the difference?
>
> Alistair
>
>
>
> -----Original Message-----
> From: Cato, Christopher [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, January 10, 2001 3:04 PM
> To: '[EMAIL PROTECTED]'
> Subject: ?? Hardware Recommendations + Database replication, any ideas
> ??
>
>
> Hello.
>
> I'd appreciate some advice from the pro's on what hardware to buy for a
> certain web application. The system in question is a commerce system based
> on JDK 1.3, TomCat, Apache and MySQL, run on Red Hat Linux 6.2 (we need to
> stick to that OS and version.) and is built as servlets.
>
> The system is targeted towards max 1000 users, probably max 100 concurrent
> users.
> The requirements are that it should be failsafe (i.e. replica server2
> replaces server1 on crash)
> and it should be fully recoverable in event of total crash.
>
> So, my questions are really:
> - What kind of hardware is required to meet the demands of the user load?
> (1000 users, 100 max concurrent)
>
> - How does one set up the replication between the servers?
> - How to determine (and switch) the servers in the event of a crash?
> - Any ideas on how to do the backup system required for this?
>
> I'd be thankful for some advice on this....
>
>
> /Christopher Cato
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
