This document discusses ditching middleware in favor of a NoSQL approach. It notes that NoSQL solutions are defined by what they don't contain compared to traditional databases. The document also discusses how data model changes can affect all tiers of an application from presentation to data schema. It provides examples of using a controller model to access data without middleware layers.
2. #nosql, like organic food, is defined
by what it doesn't contain.
Comparing noSQL solutions is like
comparing organic apples and
oranges...
Eric van der Vlist
@evlist
25 July 2011
3.
4. l
l
l
Data Access Business Logic Presentation Logic
13. Controller
RDF Store
Web server
HTTP GET Class
Resource
request
Viewable
RDF response
SPARQL query XML Template
template apply.xsl
Engine
HTTP
response HTML
21. HTTP GET
e.g. c
302 (Found)
PURL
l
i
Service
e HTTP GET
n Web
t 200 (OK)
Service
22. Data Master
Normal Ops
Dynamic
DNS
Failover /
Spillover
Data Slave
23. PURL Services
by different parties
A.org
Normal Ops
for A.org
Write-Segmented
Dynamic
data source DNS
B.com
e.g. Failover /
Spillover
for A.org
C.net