COmanage Developers List

[Benn Oshrin <>]

I'd be interested in some feedback or discussion about two different 
models for the implementation of COordinate (the backend 
middleware-esque engine).

The lighter weight approach is very much similar to the existing demo, 
with almost all data stored in third-party applications such as LDAP, 
Grouper, etc.  The advantages of this approach include faster 
implementation and no need for a SQL Server.

The heavier weight approach starts to look a little more like a 
traditional institutional identity management system, including an 
underlying SQL database for most or all data.  The advantages of this 
approach include abstraction away from specific technologies, as well as 
easier integration for more sophisticated needs (such as reporting servers).

A third model would be a hybrid or pluggable approach, but for purposes 
of this thread I think it makes sense to focus on the two ends of the 
spectrum.

To the extent possible, I'd like to consider these options in the 
context of the requirements of the entities likely to run this software, 
including DIY COs such as LIGO and CaaS providers such as Penn State for 
ESWN.

Thoughts?

-Benn-