[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: Write-intensive LDAP

tir, 2002-09-17 kl. 19:42 skrev Booker C. Bense:

> - Read the protocol more closely. There is no support for transactions
> or locking. You will have a hard time building a robust system with
> lot's of writes without those primatives. Any system that writes
> extensively to LDAP needs to support a complete rollback/queueing
> implementation outside of the protocol. Speed is not the problem,
> consistancy is what will bite you in the long run. LDAP works fine
> for WIRM applications ( write infrequently read many), it breaks
> horribly for write intensive applications.

This hasn't got much to do with the protocol IMHO, everything to do with
the choice of database. BDB 4.0.14 does, indeed, have fine-grained
locking and transactional (roll-back) logging.

I can completely rebuild my Openldap 2.1.14 database from the latest
(db_checked) log file and nothing else - nuts to those who think that
slapcat and slapadd are sufficient for making backups.

And 2.1.14 is umpteen times as fast as 2.1.13, too.

For that matter, at least at the last telling, MySQL doesn't have
transactional logging, so what?




Tony Earnshaw

Tha can allway tell a Yorkshireman, but tha canna tell 'im much.

e-post:		tonni@billy.demon.nl
www:		http://www.billy.demon.nl
gpg public key:	http://www.billy.demon.nl/tonni.armor

Telefoon:	(+31) (0)172 530428
Mobiel:		(+31) (0)6 51153356

GPG Fingerprint = 3924 6BF8 A755 DE1A 4AD6 FA2B F7D7 6051 3BE7 B981

Attachment: signature.asc
Description: Dette er en digitalt signert meldingsdel

Attachment: signature.asc
Description: Dette er en digitalt signert meldingsdel