Deployment and usage patterns

The following deployment patterns have been seen in Enterprises that deploy Social Software. Both the Social Platform software and any integrating Software are included below as they can provide separate reference points.
Deployment style has minimal effect on deciding the functionality required for the Social API, however there may be an impact when discussing implementation requirements, especially in terms of any authorization and/or request flows

Closed on-premises fully trusted deployment

Social Application
Internal collaboration only
Fully trusted system
Requirement that unnecessary authorization and corresponding overhead be avoided
Example : Provision of internal file-sharing, wiki and microblogging capability for a large bank

Closed on-premises fully trusted client

Separate application that acts as a fully trusted client of above (see Integration usage pattern)
Again requirement that unnecessary authorization and corresponding overhead be avoided
Example : Moderation/compliance provider for closed deployment above

Open on-premises

Social information presented internally
Selected information presented externally with clear markup of what is exposed
All API access reflects the above
Example : Business that socialises internally but also requires file sharing with trusted external parties (such as accountants or legal services)

Customer facing on-premises

Social information presented externally
All information is presumed externally visible by default
Selected data may be 'taken' private when required
Example : Retail business that wants to both deliver information and foster an active customer community

Open enterprise cloud

Typically as per Open on-Premises but with support for multiple organizations
Additional level of inter organisation trust ('vouched for' by host)
Example : IBM Connections Cloud