2-tier web architecture?
In Couchbase Server 2.0, the documentation and promotional material seems to favour use of a seperate web application server sitting in front of Couchbase Server (rather than just a proxy). In addition, most of the client "driver" libraries seem to be for server-side languages, rather than client-side script.
1. Are we right in understanding that Couchbase Server "expects" you to always use a web application tier between it and a client-side browser app?
Any reference materials about appropriate architectural patterns would be appreciated.