You are comparing apples and oranges here. The postgres db that stores config info and the need for a db in the cluster to provide registration and authentication info to the running proxies are two entirely different things - have nothing to do with each other at all. What if you wanted to run a large number of redundant proxy nodes, all load sharing? There are people who put Oracle DBs in the middle of such clusters and it was not (and still isnt) pretty. Following Douglas's concept we will end up with simply the most flexible and most scalable SIP session router (as if we didn't have that already), that offers branch survivability on the fly. Matt recently talked about his need to serve upwards of a 100 clinics with a centralized system but local (SIP) trunks - that's what this will do. --martin
> -----Original Message----- > From: [email protected] [mailto:sipx-dev- > [email protected]] On Behalf Of Flatfender > Sent: Monday, September 13, 2010 9:18 PM > To: sipXecs developer discussions > Subject: Re: [sipx-dev] Request for comments regarding system > performanceand how it's related to configuration > > +1 for everything being in one DB. I'm not saying mongoDB doesn't > have distinct advantages over PostgreSQL. But for a sake of > simplicity, having everything in one DB makes a lot of sense. I'm > not a big fan of most things are here, but oh yeah this one thing is > over here, and this other thing is over here. I wouldn't want to be > in the position of trying to restore a down phone server and only > having part of it b/c yeah there was these 2-3 things that are > different than you would expect. I realize I don't have a lot of sipx > experience, but I've had to rebuild/migrate enough systems to know > that consistency and simplicity is a major win. > > > Matt P. > > On Mon, Sep 13, 2010 at 1:31 PM, Michal Bielicki > <[email protected]> wrote: > > > > Am 13.09.2010 um 18:13 schrieb Matt White: > > > >>>> Douglas Hubler 09/13/10 10:35 AM >>> > >>>> > >>>>MongoDB would not replace the configuration system's database, > currently > >>>> using postgres. > > > > Whats the disadvantage to moving these DB's to Postgres like the > > configuration database? That would unifiy the databases into a > single > > engine. Postgres so far has proven to be stable and relativly > quick....and > > theres a fair bit of tuning that can be had for postgres thats not > done on > > the iso now. > > > > +1. Postgresql never failed me and we run a telco for a customer > where > > postgresql is the backend and the life cdr database for > 4000 lines. > No > > issues. I don't understand why we should use anything else. > > > > -M > > > > > > _______________________________________________ > > sipx-dev mailing list > > [email protected] > > List Archive: http://list.sipfoundry.org/archive/sipx-dev/ > > > > Michal Bielicki > > Geschäftsführer / CEO > > > > Seventh Signal Ltd. & Co. KG > > Meiereifeld 2A > > 14532 Kleinmachnow > > Büro Berlin: > > Weigandufer 45, Büro 115 > > 12059 Berlin > > Amtsgericht Potsdam HRA 4866 P, Ust.-ID: DE266981999 > > Geschäftsführer: Michal Bielicki > > Persönlich Haftende Gesellschafterin: > > Seventh Signal Ltd, 69 Great Hampton St. Birmingham, > > B18 6EW, GB, Company Nr.: 06889439 > > WWW.: http://www.seventhsignal.de > > > > _______________________________________________ > > sipx-dev mailing list > > [email protected] > > List Archive: http://list.sipfoundry.org/archive/sipx-dev/ > > > _______________________________________________ > sipx-dev mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-dev/ _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev/
