[asterisk-users] When does Scalability requests Asterisk to U se SER ?

[Rushowr]

adebayo omo-dare wrote:
> Hi Sheerwood,
> I unfortunately saw a bit of what I percieve to be an error in what you
> said. BerkeleyDB does in fact support replication across nodes - see:
> http://www.sleepycat.com/docs/ref/rep/intro.html - possibly you meant to
> say the version implemented in * does not support replication. If so, I
> do appoligise for being a little pedantic.
>  
> I have only just started to look at *'s code - so what I say further is
> with a great deal of hesitation when directly referenced to *. However,
> I work with both Berkely (on a programming level) and MySQL in a telecom
> (soft-switch) environment.
>  
> In terms of performance (judged as speed), a comparison between MySQL
> and Berkeley would be like comparing a top of the range Mercedes to an
> F1 racing car. Overheads from MySQL come in the form of SQL translation,
> use of Sockets, etc... This is in addition to its size.
>  
> Yet, the choice between the two, is a lot more complex, IMHO, than
> mereley thinking in terms of performance. And possible High Availability
> solutions, in their own rights, taking in to consideration that * will
> be working in concert with numerous other environments, programmes and
> requirments, are diverse enough to make each deployment a little unique
> - thereby making each option a potential liability.
>  
> One rule of thumb for us has always been - if you need raw speed, and
> intend to deal with the data in a very restricted/rigid/"well
> defined" manner - opt for Berkeley. But if you want a great deal of
> fluidity, and intend, or may at some time intend, for that data to
> interact with other applications and potential requirements - Opt MySQL.
>  
> It is possibly also best to work with what you feel most comfortable
> with first and then experiment to see if you may require the services of
> the other.
>  
> ps. In terms of querying a DB for every call, I would presume that a DB
> is an active and fragile thing and the provision of ACID ensures that
> everything that occurs with it does so with a certain measure of safety.
> In fact, due to the random manner of requests, you will find it, in
> complete terms, actually performs a lot better than any other form of
> retrieval.
>  
> Hope this, in some manner, helps
> Bayo

Bayo,
Thanks for your input! I was actually not aware that Berkley DB allowed
replication.

The primary reason for using MySQL (and PostgreSQL in some of my other
projects) is the ease with which you can have the data used in other
systems.

Thanks again for your input :)

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 187 bytes
Desc: OpenPGP digital signature
Url : http://lists.digium.com/pipermail/asterisk-users/attachments/20060920/4b1d5363/signature.pgp