469,903 Members | 1,398 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,903 developers. It's quick & easy.

Dividing (load-balancing) db entries among backend servers


I am in the process of designing the following kind of system --

A MySQL database holds hundreds of thousands of entries. All of these
entries are periodically processed by a set of backends. Whenever an
entry is processed, its related fields are updated.

The approaches I am considering for load-balancing are:

1. Have a backend-id associated with each entry. Each backend server
is given
a range of backend-ids it should process. I don't like this for the
reason that
if someone messes up backend-id range allocation among backends, some
entries may not get processed at all (or, could get processed multiple

2. No backend-ids. Each backend server grabs a bunch of unprocessed
entries by
updating a status field. Once it is done processing all of them, it
again updates the status to signal the completion of the processing.
This approach results in two updates to every record in a processing
cycle. Also, it is tricky
to grab unprocessed records (since they may have just been processed
by other backend).

Do I have any other choices apart from above? I would highly
appreciate any ideas.

Jul 19 '05 #1
0 1455

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

4 posts views Thread by Socheat Sou | last post: by
reply views Thread by Robert Treat | last post: by
2 posts views Thread by Jay Balapa | last post: by
3 posts views Thread by Henrik Lied | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.