[RADIATOR] searchable archive? CouchDB?

[Dave Kitabjian]

See replies...

-----Original Message-----
From: Heikki Vatiainen [mailto:hvn at open.com.au] 
Sent: Tuesday, October 11, 2011 9:01 AM
To: Dave Kitabjian
Cc: radiator at open.com.au; Greg Evanyke
Subject: Re: [RADIATOR] searchable archive? CouchDB?

[dhk] ...

>> 2)   Is there an AuthBy that will talk to *CouchDB* or *MongoDB*?

> [dhk] Well, at this point, the main attraction to some of these No-SQL
> products is their robust replication support particularly as a
> peer-to-peer architecture (rather than Master-Slave, like LDAP). We
are
> looking for the Auth side at this point, not the Accounting side.

I took a look at Perl support and there seems not to be anything for
NoSQL that is like DBI for SQL. So not common layer for different NoSQL
DBs. This would mean the support would need to written for either or.

[dhk] Yes, I did a quick look and found the same thing, which I thought
was odd considering the growing popularity of NoSQL and the otherwise
broad range of modules at CPAN.

Can you tell which one would be more suitable for RADIUS type of AAA
use?

[dhk] We don't know enough to answer that at this point. But the point
you made earlier was the same as I was thinking: RADIUS Accounting
packets and their varying range of attributes make them a natural fit
for the "no schema" approach. And the "evenually consistent" integrity
model is fine for most applications of Accounting records. I like the
bi-directional sync with conflict resolution of CouchDB, but I'm not
sure eventual consistency is robust enough for keeping a Session table
up to date; but it would be fine for the Auth db, as in your LDAP
support. 

Dave

CONFIDENTIALITY NOTICE***The information contained in this message may be 
privileged, confidential, and protected from disclosure. If the reader of 
this message is not the intended recipient, or any employee or agent 
responsible for delivering this message to the intended recipient, you are 
hereby notified that any dissemination, distribution, or copying of this 
communication is strictly prohibited. If you have received this 
communication in error, please notify us immediately by replying to the 
message and deleting it from your computer. Thank you.