There has been a lot of talk and discussion on  Rainbow versions such as Rainbow 2.0 Lite.    I want to form a simple outline if you will of what I think should go in each version and its target audience.

Rainbow Portal 2.0 Lite :

 Target Audience : The everyday web user who wishes to display html content using CMS concepts.

Modules :  HTML, Pics, Discussion,Forum, etc - no more than 20
               - all modules in same db

DB :  any supported rainbow 1.1 db such as access, SQL Server 2000/2005 , maybe oracle

Login layer :  none


Auth :  Forms

Rainbow Portal 2.0 Standard:

 Target Audience : Small to mid-sized businesses who have content updaters

Modules :  Lite + small mid-sized talored mods  - no more than 50
               option 1: all mods in same rainbow db
               option 2: all mods in different db

DB :  option 1 : SQL Server 2005 family [ express, dev, ent , etc] - allows for login layer
         option 2: Lite configuration

Login layer : only if option 1 is met - ASPNET db will be inside of rainbow db.


Auth : Windows Auth | Forms

Rainbow Portal 2.0 Enterprise :

 Target Audience :  Corporate customers : Intranet / Extranet

Modules :  Standard + corporate centric mods - no more than 60
                 - all modules in their own db

DB :  SQL Server 2000/2005
      option 1: 2005 w/ XML node support
      option 2: 2000 with no xml node support

Login layer :  ASPNETDB stored in totally diffrent db

Auth : Windows Auth | Forms | AD | LDAP


With enterprise, I take the login layer completly out of rainbow as well as the modules.  This allows you to have just rainbow portal running in its own database set with 2 providers controlling your login/modules.  This is the set I favor.

Rahul noted to me that Ecommerce should be an edt of its own and I agree.  Maybe a far future Rainbow Portal 2.0 E-commerce Edition.