Reaching for that SQL database for your next project? Think again! Maybe a non-SQL database is for you!

1. Forget the ORM!
Persistent data with
Non-traditional Databases
By Randal L. Schwartz,
Stonehenge Consulting Services, Inc.
<merlyn@stonehenge.com>
http://www.stonehenge.com/merlyn/
version 1.2 at 13 April 2010

2. What we are covering

3. What we are covering
• What is an Object-Relational-Mapper?

4. What we are covering
• What is an Object-Relational-Mapper?
• Why is it evil?

5. What we are covering
• What is an Object-Relational-Mapper?
• Why is it evil?
• What are the alternatives?

6. Brief review of ORMs

7. Brief review of ORMs
• Objects in memory

8. Brief review of ORMs
• Objects in memory
• Tables in RDBMS

9. Brief review of ORMs
• Objects in memory
• Tables in RDBMS
• Load objects from tables

10. Brief review of ORMs
• Objects in memory
• Tables in RDBMS
• Load objects from tables
• Store objects (and changes) back to tables

11. Brief review of ORMs
• Objects in memory
• Tables in RDBMS
• Load objects from tables
• Store objects (and changes) back to tables
• Typically mapped one attribute per column

12. Brief review of ORMs
• Objects in memory
• Tables in RDBMS
• Load objects from tables
• Store objects (and changes) back to tables
• Typically mapped one attribute per column
• Occasionally more complex mappings

13. But things change

14. But things change
• Object attributes get updated

15. But things change
• Object attributes get updated
• New objects get created

16. But things change
• Object attributes get updated
• New objects get created
• Need to map that back to the RDB

17. But things change
• Object attributes get updated
• New objects get created
• Need to map that back to the RDB
• Updates often require custom SQL

18. But things change
• Object attributes get updated
• New objects get created
• Need to map that back to the RDB
• Updates often require custom SQL
• Or live with updating more than needed

19. But things change
• Object attributes get updated
• New objects get created
• Need to map that back to the RDB
• Updates often require custom SQL
• Or live with updating more than needed
• Detecting what has changed can be hard

20. One-to-many messes

21. One-to-many messes
• Messy when an attribute is a reference

22. One-to-many messes
• Messy when an attribute is a reference
• Or a non-DB data type, like a set

23. One-to-many messes
• Messy when an attribute is a reference
• Or a non-DB data type, like a set
• Mapping involves joins

24. One-to-many messes
• Messy when an attribute is a reference
• Or a non-DB data type, like a set
• Mapping involves joins
• Left joins to get child rows

25. One-to-many messes
• Messy when an attribute is a reference
• Or a non-DB data type, like a set
• Mapping involves joins
• Left joins to get child rows
• Or multiple trips to get joined data

26. One-to-many messes
• Messy when an attribute is a reference
• Or a non-DB data type, like a set
• Mapping involves joins
• Left joins to get child rows
• Or multiple trips to get joined data
• Either way, expensive

27. Why this is bad

28. Why this is bad
• If your car were an ORM...

29. Why this is bad
• If your car were an ORM...
• Reduce it to parts each night in garage

30. Why this is bad
• If your car were an ORM...
• Reduce it to parts each night in garage
• Rebuild it each morning

31. Why this is bad
• If your car were an ORM...
• Reduce it to parts each night in garage
• Rebuild it each morning
• Is this sane in the 21st century?

32. Why this is bad
• If your car were an ORM...
• Reduce it to parts each night in garage
• Rebuild it each morning
• Is this sane in the 21st century?
• Most ORMs generate the SQL on the fly

33. Why this is bad
• If your car were an ORM...
• Reduce it to parts each night in garage
• Rebuild it each morning
• Is this sane in the 21st century?
• Most ORMs generate the SQL on the fly
• Recompiling text on each hit?

34. Why this is bad
• If your car were an ORM...
• Reduce it to parts each night in garage
• Rebuild it each morning
• Is this sane in the 21st century?
• Most ORMs generate the SQL on the fly
• Recompiling text on each hit?
• Often called the “object relational
impedence mismatch”

35. How to solve it

36. How to solve it
• Rectangles don’t fit today’s data

37. How to solve it
• Rectangles don’t fit today’s data
• Solution: Don’t store rectangles

38. How to solve it
• Rectangles don’t fit today’s data
• Solution: Don’t store rectangles
• Also known as “NoSQL” solutions

39. How to solve it
• Rectangles don’t fit today’s data
• Solution: Don’t store rectangles
• Also known as “NoSQL” solutions
• Two main options:

40. How to solve it
• Rectangles don’t fit today’s data
• Solution: Don’t store rectangles
• Also known as “NoSQL” solutions
• Two main options:
• Document storage (typically JSON)

41. How to solve it
• Rectangles don’t fit today’s data
• Solution: Don’t store rectangles
• Also known as “NoSQL” solutions
• Two main options:
• Document storage (typically JSON)
• Object storage

42. How to solve it
• Rectangles don’t fit today’s data
• Solution: Don’t store rectangles
• Also known as “NoSQL” solutions
• Two main options:
• Document storage (typically JSON)
• Object storage
• (Generally) not possible if other apps still
need the data as RDB

43. Dropping ACID

44. Dropping ACID
• Automicity, Consistency, Isolation,
Durability

45. Dropping ACID
• Automicity, Consistency, Isolation,
Durability
• Often expressed through transactions

46. Dropping ACID
• Automicity, Consistency, Isolation,
Durability
• Often expressed through transactions
• Most NoSQL offer no multi-update ACID

47. Dropping ACID
• Automicity, Consistency, Isolation,
Durability
• Often expressed through transactions
• Most NoSQL offer no multi-update ACID
• But atomic within a single doc update

48. Dropping ACID
• Automicity, Consistency, Isolation,
Durability
• Often expressed through transactions
• Most NoSQL offer no multi-update ACID
• But atomic within a single doc update
• Thus, think about your “schema” carefully

49. Dropping ACID
• Automicity, Consistency, Isolation,
Durability
• Often expressed through transactions
• Most NoSQL offer no multi-update ACID
• But atomic within a single doc update
• Thus, think about your “schema” carefully
• Ensure single doc update suffices

50. Eric Brewer’s CAP

51. Eric Brewer’s CAP
• Consistency

52. Eric Brewer’s CAP
• Consistency
• All working, or not working

53. Eric Brewer’s CAP
• Consistency
• All working, or not working
• Yes, this is the “A” in ACID

54. Eric Brewer’s CAP
• Consistency
• All working, or not working
• Yes, this is the “A” in ACID
• Availability

55. Eric Brewer’s CAP
• Consistency
• All working, or not working
• Yes, this is the “A” in ACID
• Availability
• Is the service up and running?

56. Eric Brewer’s CAP
• Consistency
• All working, or not working
• Yes, this is the “A” in ACID
• Availability
• Is the service up and running?
• Partition Tolerance

57. Eric Brewer’s CAP
• Consistency
• All working, or not working
• Yes, this is the “A” in ACID
• Availability
• Is the service up and running?
• Partition Tolerance
• Can parts of it go offline safely?

58. Eric Brewer’s CAP
• Consistency
• All working, or not working
• Yes, this is the “A” in ACID
• Availability
• Is the service up and running?
• Partition Tolerance
• Can parts of it go offline safely?
• .... Pick any two

59. Current solutions

60. Current solutions
• Document store

61. Current solutions
• Document store
• Graph

62. Current solutions
• Document store
• Graph
• Key/Value in RAM/Disk

63. Current solutions
• Document store
• Graph
• Key/Value in RAM/Disk
• Key/Value on Disk

64. Current solutions
• Document store
• Graph
• Key/Value in RAM/Disk
• Key/Value on Disk
• Tabular

65. Current solutions
• Document store
• Graph
• Key/Value in RAM/Disk
• Key/Value on Disk
• Tabular
• Object Database

66. Document Store

67. Document Store
• CouchDB

68. Document Store
• CouchDB
• MongoDB

69. Document Store
• CouchDB
• MongoDB
• Apache Jackrabbit

70. Document Store
• CouchDB
• MongoDB
• Apache Jackrabbit
• XML Databases

71. Document Store
• CouchDB
• MongoDB
• Apache Jackrabbit
• XML Databases
• MarkLogic Server

72. Document Store
• CouchDB
• MongoDB
• Apache Jackrabbit
• XML Databases
• MarkLogic Server
• GemFire

73. Document Store
• CouchDB
• MongoDB
• Apache Jackrabbit
• XML Databases
• MarkLogic Server
• GemFire
• eXist

74. CouchDB

75. CouchDB
• Open source (Erlang, Apache 2.0)

76. CouchDB
• Open source (Erlang, Apache 2.0)
• Stores JSON documents

77. CouchDB
• Open source (Erlang, Apache 2.0)
• Stores JSON documents
• Uses SpiderMonkey for processing

78. CouchDB
• Open source (Erlang, Apache 2.0)
• Stores JSON documents
• Uses SpiderMonkey for processing
• Provides “views”

79. CouchDB
• Open source (Erlang, Apache 2.0)
• Stores JSON documents
• Uses SpiderMonkey for processing
• Provides “views”
• Aggregate functions

80. CouchDB
• Open source (Erlang, Apache 2.0)
• Stores JSON documents
• Uses SpiderMonkey for processing
• Provides “views”
• Aggregate functions
• Scales with map/reduce

81. CouchDB
• Open source (Erlang, Apache 2.0)
• Stores JSON documents
• Uses SpiderMonkey for processing
• Provides “views”
• Aggregate functions
• Scales with map/reduce
• RESTful API

82. CouchDB
• Open source (Erlang, Apache 2.0)
• Stores JSON documents
• Uses SpiderMonkey for processing
• Provides “views”
• Aggregate functions
• Scales with map/reduce
• RESTful API
• FLOSS Weekly #36

83. MongoDB

84. MongoDB
• Open source (C++, GNU AGPL3)

85. MongoDB
• Open source (C++, GNU AGPL3)
• Wire/Storage protocol is BSON

86. MongoDB
• Open source (C++, GNU AGPL3)
• Wire/Storage protocol is BSON
• Embedded JavaScript for map/reduce

87. MongoDB
• Open source (C++, GNU AGPL3)
• Wire/Storage protocol is BSON
• Embedded JavaScript for map/reduce
• Interactive JavaScript shell

88. MongoDB
• Open source (C++, GNU AGPL3)
• Wire/Storage protocol is BSON
• Embedded JavaScript for map/reduce
• Interactive JavaScript shell
• In-place updates

89. MongoDB
• Open source (C++, GNU AGPL3)
• Wire/Storage protocol is BSON
• Embedded JavaScript for map/reduce
• Interactive JavaScript shell
• In-place updates
• Replication

90. MongoDB
• Open source (C++, GNU AGPL3)
• Wire/Storage protocol is BSON
• Embedded JavaScript for map/reduce
• Interactive JavaScript shell
• In-place updates
• Replication
• Auto-sharding

91. MongoDB
• Open source (C++, GNU AGPL3)
• Wire/Storage protocol is BSON
• Embedded JavaScript for map/reduce
• Interactive JavaScript shell
• In-place updates
• Replication
• Auto-sharding
• Bindings for many languages

92. MongoDB
• Open source (C++, GNU AGPL3)
• Wire/Storage protocol is BSON
• Embedded JavaScript for map/reduce
• Interactive JavaScript shell
• In-place updates
• Replication
• Auto-sharding
• Bindings for many languages
• FLOSS Weekly #105

93. Apache Jackrabbit

94. Apache Jackrabbit
• Open source (Java, Apache 2.0)

95. Apache Jackrabbit
• Open source (Java, Apache 2.0)
• XML content on disk

96. Apache Jackrabbit
• Open source (Java, Apache 2.0)
• XML content on disk
• Implements Java Content Repository API

97. Apache Jackrabbit
• Open source (Java, Apache 2.0)
• XML content on disk
• Implements Java Content Repository API
• Full text and XPath search

98. Apache Jackrabbit
• Open source (Java, Apache 2.0)
• XML content on disk
• Implements Java Content Repository API
• Full text and XPath search
• Versioning, transactions, observation

99. Apache Jackrabbit
• Open source (Java, Apache 2.0)
• XML content on disk
• Implements Java Content Repository API
• Full text and XPath search
• Versioning, transactions, observation
• Authentication

100. Apache Jackrabbit
• Open source (Java, Apache 2.0)
• XML content on disk
• Implements Java Content Repository API
• Full text and XPath search
• Versioning, transactions, observation
• Authentication
• Object persistence using Object Content
Manager

101. MarkLogic Server

102. MarkLogic Server
• Not open-source

103. MarkLogic Server
• Not open-source
• XML database

104. MarkLogic Server
• Not open-source
• XML database
• Implements XQuery

105. MarkLogic Server
• Not open-source
• XML database
• Implements XQuery
• Full-text and structured search

106. MarkLogic Server
• Not open-source
• XML database
• Implements XQuery
• Full-text and structured search
• Native geospatial searches

107. MarkLogic Server
• Not open-source
• XML database
• Implements XQuery
• Full-text and structured search
• Native geospatial searches
• In heavy use by their customers

108. MarkLogic Server
• Not open-source
• XML database
• Implements XQuery
• Full-text and structured search
• Native geospatial searches
• In heavy use by their customers
• Scalable to “hundreds of terabytes”

109. MarkLogic Server
• Not open-source
• XML database
• Implements XQuery
• Full-text and structured search
• Native geospatial searches
• In heavy use by their customers
• Scalable to “hundreds of terabytes”
• Both native and RESTful APIs

110. GemFire

111. GemFire
• Not open-source

112. GemFire
• Not open-source
• Mostly-in-memory distributed object cache

113. GemFire
• Not open-source
• Mostly-in-memory distributed object cache
• Change notification

114. GemFire
• Not open-source
• Mostly-in-memory distributed object cache
• Change notification
• Highly available

115. GemFire
• Not open-source
• Mostly-in-memory distributed object cache
• Change notification
• Highly available
• Object Query Language compatible

116. GemFire
• Not open-source
• Mostly-in-memory distributed object cache
• Change notification
• Highly available
• Object Query Language compatible
• Native Java/C++/C# objects

117. GemFire
• Not open-source
• Mostly-in-memory distributed object cache
• Change notification
• Highly available
• Object Query Language compatible
• Native Java/C++/C# objects
• Persistence to file system, databases, etc

118. eXist

119. eXist
• Open source (Java, LGPL)

120. eXist
• Open source (Java, LGPL)
• Native XML queries

121. eXist
• Open source (Java, LGPL)
• Native XML queries
• XQuery, XPath, XSLT, XUpdate

122. eXist
• Open source (Java, LGPL)
• Native XML queries
• XQuery, XPath, XSLT, XUpdate
• Rich APIs: REST, WebDAV, SOAP

123. eXist
• Open source (Java, LGPL)
• Native XML queries
• XQuery, XPath, XSLT, XUpdate
• Rich APIs: REST, WebDAV, SOAP
• Can serve entire webapps!

124. eXist
• Open source (Java, LGPL)
• Native XML queries
• XQuery, XPath, XSLT, XUpdate
• Rich APIs: REST, WebDAV, SOAP
• Can serve entire webapps!
• Used by large installations

125. eXist
• Open source (Java, LGPL)
• Native XML queries
• XQuery, XPath, XSLT, XUpdate
• Rich APIs: REST, WebDAV, SOAP
• Can serve entire webapps!
• Used by large installations
• US State Department (history.state.gov)

126. eXist
• Open source (Java, LGPL)
• Native XML queries
• XQuery, XPath, XSLT, XUpdate
• Rich APIs: REST, WebDAV, SOAP
• Can serve entire webapps!
• Used by large installations
• US State Department (history.state.gov)
• FLOSS Weekly #97

127. Graph

128. Graph
• InfoGrid

129. Graph
• InfoGrid
• Neo4J

130. Graph
• InfoGrid
• Neo4J
• AllegroGraph

131. InfoGrid

132. InfoGrid
• Open source (Java, AGPL3)

133. InfoGrid
• Open source (Java, AGPL3)
• GraphDatabase stores nodes and edges

134. InfoGrid
• Open source (Java, AGPL3)
• GraphDatabase stores nodes and edges
• MeshBase - self contained

135. InfoGrid
• Open source (Java, AGPL3)
• GraphDatabase stores nodes and edges
• MeshBase - self contained
• NetMeshBase - distributed knowledge

136. InfoGrid
• Open source (Java, AGPL3)
• GraphDatabase stores nodes and edges
• MeshBase - self contained
• NetMeshBase - distributed knowledge
• API in front of other SQL and NoSQL DBs

137. InfoGrid
• Open source (Java, AGPL3)
• GraphDatabase stores nodes and edges
• MeshBase - self contained
• NetMeshBase - distributed knowledge
• API in front of other SQL and NoSQL DBs
• Includes components for authentication

138. Neo4j

139. Neo4j
• Open source (Java, AGPL3)

140. Neo4j
• Open source (Java, AGPL3)
• Commercial support/version available

141. Neo4j
• Open source (Java, AGPL3)
• Commercial support/version available
• Java objects on disk

142. Neo4j
• Open source (Java, AGPL3)
• Commercial support/version available
• Java objects on disk
• Transactional

143. Neo4j
• Open source (Java, AGPL3)
• Commercial support/version available
• Java objects on disk
• Transactional
• Scalable (several billion nodes on single
machine)

144. Neo4j
• Open source (Java, AGPL3)
• Commercial support/version available
• Java objects on disk
• Transactional
• Scalable (several billion nodes on single
machine)
• Small footprint (JAR under 500KB)

145. Neo4j
• Open source (Java, AGPL3)
• Commercial support/version available
• Java objects on disk
• Transactional
• Scalable (several billion nodes on single
machine)
• Small footprint (JAR under 500KB)
• RDF mappings

146. AllegroGraph

147. AllegroGraph
• Free versions (not open source)

148. AllegroGraph
• Free versions (not open source)
• Holds Resource Description Frameworks

149. AllegroGraph
• Free versions (not open source)
• Holds Resource Description Frameworks
• From Franz, Inc (Franz Lisp, etc)

150. AllegroGraph
• Free versions (not open source)
• Holds Resource Description Frameworks
• From Franz, Inc (Franz Lisp, etc)
• Interfaces in many common languages

151. AllegroGraph
• Free versions (not open source)
• Holds Resource Description Frameworks
• From Franz, Inc (Franz Lisp, etc)
• Interfaces in many common languages
• Active development

152. AllegroGraph
• Free versions (not open source)
• Holds Resource Description Frameworks
• From Franz, Inc (Franz Lisp, etc)
• Interfaces in many common languages
• Active development
• In use by FLOSS/commercial/government

153. AllegroGraph
• Free versions (not open source)
• Holds Resource Description Frameworks
• From Franz, Inc (Franz Lisp, etc)
• Interfaces in many common languages
• Active development
• In use by FLOSS/commercial/government
• Queries with SPARQL

154. AllegroGraph
• Free versions (not open source)
• Holds Resource Description Frameworks
• From Franz, Inc (Franz Lisp, etc)
• Interfaces in many common languages
• Active development
• In use by FLOSS/commercial/government
• Queries with SPARQL
• ... Protocol and RDF Query Language

155. Key/Value in RAM/Disk

156. Key/Value in RAM/Disk
• memcached

157. Key/Value in RAM/Disk
• memcached
• Redis

158. Memcached

159. Memcached
• Open source (C, BSD)

160. Memcached
• Open source (C, BSD)
• LRU cache (data may be lost)

161. Memcached
• Open source (C, BSD)
• LRU cache (data may be lost)
• Developed for LiveJournal

162. Memcached
• Open source (C, BSD)
• LRU cache (data may be lost)
• Developed for LiveJournal
• used by many large sites

163. Memcached
• Open source (C, BSD)
• LRU cache (data may be lost)
• Developed for LiveJournal
• used by many large sites
• Simple key/value storage

164. Memcached
• Open source (C, BSD)
• LRU cache (data may be lost)
• Developed for LiveJournal
• used by many large sites
• Simple key/value storage
• Keys up to 120 bytes, values 1 MB

165. Memcached
• Open source (C, BSD)
• LRU cache (data may be lost)
• Developed for LiveJournal
• used by many large sites
• Simple key/value storage
• Keys up to 120 bytes, values 1 MB
• Clientside horizontal scaling

166. Memcached
• Open source (C, BSD)
• LRU cache (data may be lost)
• Developed for LiveJournal
• used by many large sites
• Simple key/value storage
• Keys up to 120 bytes, values 1 MB
• Clientside horizontal scaling
• Can also store on disk (memcachedb)

167. Redis

168. Redis
• Open source (C, BSD)

169. Redis
• Open source (C, BSD)
• Development funded by VMWare

170. Redis
• Open source (C, BSD)
• Development funded by VMWare
• Similar to Memcached (key/value pair)

171. Redis
• Open source (C, BSD)
• Development funded by VMWare
• Similar to Memcached (key/value pair)
• Values can be lists, sets, hashes

172. Redis
• Open source (C, BSD)
• Development funded by VMWare
• Similar to Memcached (key/value pair)
• Values can be lists, sets, hashes
• Master/slave replication supported

173. Redis
• Open source (C, BSD)
• Development funded by VMWare
• Similar to Memcached (key/value pair)
• Values can be lists, sets, hashes
• Master/slave replication supported
• Many client languages available

174. Redis
• Open source (C, BSD)
• Development funded by VMWare
• Similar to Memcached (key/value pair)
• Values can be lists, sets, hashes
• Master/slave replication supported
• Many client languages available
• Used by many big sites

175. Redis
• Open source (C, BSD)
• Development funded by VMWare
• Similar to Memcached (key/value pair)
• Values can be lists, sets, hashes
• Master/slave replication supported
• Many client languages available
• Used by many big sites
• Github, Craigslist, Engine Yard, Guardian

176. Redis
• Open source (C, BSD)
• Development funded by VMWare
• Similar to Memcached (key/value pair)
• Values can be lists, sets, hashes
• Master/slave replication supported
• Many client languages available
• Used by many big sites
• Github, Craigslist, Engine Yard, Guardian
• Can also store on disk

177. Key/Value on Disk

178. Key/Value on Disk
• Amazon SimpleDB

179. Key/Value on Disk
• Amazon SimpleDB
• Berkeley DB

180. Key/Value on Disk
• Amazon SimpleDB
• Berkeley DB
• Tokyo Cabinet

181. Key/Value on Disk
• Amazon SimpleDB
• Berkeley DB
• Tokyo Cabinet
• Cassandra

182. Key/Value on Disk
• Amazon SimpleDB
• Berkeley DB
• Tokyo Cabinet
• Cassandra
• GT.M

183. Amazon SimpleDB

184. Amazon SimpleDB
• Built by Amazon in Erlang

185. Amazon SimpleDB
• Built by Amazon in Erlang
• Supports EC2 applications

186. Amazon SimpleDB
• Built by Amazon in Erlang
• Supports EC2 applications
• Highly scalable

187. Amazon SimpleDB
• Built by Amazon in Erlang
• Supports EC2 applications
• Highly scalable
• “Eventual” Consistency

188. Amazon SimpleDB
• Built by Amazon in Erlang
• Supports EC2 applications
• Highly scalable
• “Eventual” Consistency
• Items have query-able attributes

189. Amazon SimpleDB
• Built by Amazon in Erlang
• Supports EC2 applications
• Highly scalable
• “Eventual” Consistency
• Items have query-able attributes
• No text search

190. Amazon SimpleDB
• Built by Amazon in Erlang
• Supports EC2 applications
• Highly scalable
• “Eventual” Consistency
• Items have query-able attributes
• No text search
• Build your own indexes

191. Berkeley DB

192. Berkeley DB
• Open source (C, Sleepycat)

193. Berkeley DB
• Open source (C, Sleepycat)
• Enhancement of original DBM from AT&T

194. Berkeley DB
• Open source (C, Sleepycat)
• Enhancement of original DBM from AT&T
• Key/value pairs in various storage formats

195. Berkeley DB
• Open source (C, Sleepycat)
• Enhancement of original DBM from AT&T
• Key/value pairs in various storage formats
• Transactional locking, HA features

196. Berkeley DB
• Open source (C, Sleepycat)
• Enhancement of original DBM from AT&T
• Key/value pairs in various storage formats
• Transactional locking, HA features
• Widely used

197. Tokyo Cabinet

198. Tokyo Cabinet
• Open source (C, LGPL)

199. Tokyo Cabinet
• Open source (C, LGPL)
• Successor to GDBM and QDBM

200. Tokyo Cabinet
• Open source (C, LGPL)
• Successor to GDBM and QDBM
• Very efficient in both space and speed

201. Tokyo Cabinet
• Open source (C, LGPL)
• Successor to GDBM and QDBM
• Very efficient in both space and speed
• Simple key/value pairs

202. Tokyo Cabinet
• Open source (C, LGPL)
• Successor to GDBM and QDBM
• Very efficient in both space and speed
• Simple key/value pairs
• Multiple storage strategies

203. Tokyo Cabinet
• Open source (C, LGPL)
• Successor to GDBM and QDBM
• Very efficient in both space and speed
• Simple key/value pairs
• Multiple storage strategies
• Multiple client language interfaces

204. Tokyo Cabinet
• Open source (C, LGPL)
• Successor to GDBM and QDBM
• Very efficient in both space and speed
• Simple key/value pairs
• Multiple storage strategies
• Multiple client language interfaces
• Local storage only: no network interface

205. Tokyo Cabinet
• Open source (C, LGPL)
• Successor to GDBM and QDBM
• Very efficient in both space and speed
• Simple key/value pairs
• Multiple storage strategies
• Multiple client language interfaces
• Local storage only: no network interface
• But see Tokyo Tyrant

206. Cassandra

207. Cassandra
• Open source (Java, Apache 2)

208. Cassandra
• Open source (Java, Apache 2)
• Originally developed at Facebook

209. Cassandra
• Open source (Java, Apache 2)
• Originally developed at Facebook
• Uses key-column-value storage

210. Cassandra
• Open source (Java, Apache 2)
• Originally developed at Facebook
• Uses key-column-value storage
• High availability/elastic through replication

211. Cassandra
• Open source (Java, Apache 2)
• Originally developed at Facebook
• Uses key-column-value storage
• High availability/elastic through replication
• Used by Facebook, Digg, Twitter, Rackspace

212. Cassandra
• Open source (Java, Apache 2)
• Originally developed at Facebook
• Uses key-column-value storage
• High availability/elastic through replication
• Used by Facebook, Digg, Twitter, Rackspace
• Eventually consistent

213. Cassandra
• Open source (Java, Apache 2)
• Originally developed at Facebook
• Uses key-column-value storage
• High availability/elastic through replication
• Used by Facebook, Digg, Twitter, Rackspace
• Eventually consistent
• Queries can ask “majority” or “all”

214. GT.M

215. GT.M
• Open Source (Mumps, GPL)

216. GT.M
• Open Source (Mumps, GPL)
• Commercial support from Fidelity

217. GT.M
• Open Source (Mumps, GPL)
• Commercial support from Fidelity
• Distributed persistence of key/value pairs

218. GT.M
• Open Source (Mumps, GPL)
• Commercial support from Fidelity
• Distributed persistence of key/value pairs
• Transactions via optimistic concurrency

219. GT.M
• Open Source (Mumps, GPL)
• Commercial support from Fidelity
• Distributed persistence of key/value pairs
• Transactions via optimistic concurrency
• Everything you read must be unchanged

220. GT.M
• Open Source (Mumps, GPL)
• Commercial support from Fidelity
• Distributed persistence of key/value pairs
• Transactions via optimistic concurrency
• Everything you read must be unchanged
• Mumps-to-C-to-Mumps APIs

221. Tabular

222. Tabular
• Mnesia

223. Tabular
• Mnesia
• Hbase

224. Tabular
• Mnesia
• Hbase
• Hypertable

225. Mnesia

226. Mnesia
• Open source (Erlang, Erlang license)

227. Mnesia
• Open source (Erlang, Erlang license)
• Key/value pairs

228. Mnesia
• Open source (Erlang, Erlang license)
• Key/value pairs
• Value is any Erlang datatype

229. Mnesia
• Open source (Erlang, Erlang license)
• Key/value pairs
• Value is any Erlang datatype
• Live reconfiguration

230. Mnesia
• Open source (Erlang, Erlang license)
• Key/value pairs
• Value is any Erlang datatype
• Live reconfiguration
• Supports transactions and distribution

231. Hbase

232. Hbase
• Open source (Java, Apache 2)

233. Hbase
• Open source (Java, Apache 2)
• Mimics Google’s “BigTable”

234. Hbase
• Open source (Java, Apache 2)
• Mimics Google’s “BigTable”
• Push map/reduce down to shards

235. Hbase
• Open source (Java, Apache 2)
• Mimics Google’s “BigTable”
• Push map/reduce down to shards
• Runs on Hadoop Distributed File System

236. Hbase
• Open source (Java, Apache 2)
• Mimics Google’s “BigTable”
• Push map/reduce down to shards
• Runs on Hadoop Distributed File System
• Java, REST, Thrift APIs

237. Hbase
• Open source (Java, Apache 2)
• Mimics Google’s “BigTable”
• Push map/reduce down to shards
• Runs on Hadoop Distributed File System
• Java, REST, Thrift APIs
• Might be the DB behind Bing

238. Hypertable

239. Hypertable
• Open source (C++, GPL 2)

240. Hypertable
• Open source (C++, GPL 2)
• Yet another BigTable clone

241. Hypertable
• Open source (C++, GPL 2)
• Yet another BigTable clone
• Designed for highly scalable data storage

242. Object database

243. Object database
• Db4o

244. Object database
• Db4o
• InterSystems Cache

245. Object database
• Db4o
• InterSystems Cache
• ZODB

246. Object database
• Db4o
• InterSystems Cache
• ZODB
• GemStone/S

247. Object database
• Db4o
• InterSystems Cache
• ZODB
• GemStone/S
• Magma

248. Db4o

249. Db4o
• Open source (Java/C#, GPL)

250. Db4o
• Open source (Java/C#, GPL)
• Commercial license/support available

251. Db4o
• Open source (Java/C#, GPL)
• Commercial license/support available
• Supports object persistence

252. Db4o
• Open source (Java/C#, GPL)
• Commercial license/support available
• Supports object persistence
• both Java and dot-net

253. Db4o
• Open source (Java/C#, GPL)
• Commercial license/support available
• Supports object persistence
• both Java and dot-net
• Can replicate to traditional RDBMS

254. Db4o
• Open source (Java/C#, GPL)
• Commercial license/support available
• Supports object persistence
• both Java and dot-net
• Can replicate to traditional RDBMS
• Supports class migration

255. Db4o
• Open source (Java/C#, GPL)
• Commercial license/support available
• Supports object persistence
• both Java and dot-net
• Can replicate to traditional RDBMS
• Supports class migration
• ... if you provide the code

256. Db4o
• Open source (Java/C#, GPL)
• Commercial license/support available
• Supports object persistence
• both Java and dot-net
• Can replicate to traditional RDBMS
• Supports class migration
• ... if you provide the code
• Large community

257. InterSystems Cache

258. InterSystems Cache
• Commercial

259. InterSystems Cache
• Commercial
• “World’s fastest object database”

260. InterSystems Cache
• Commercial
• “World’s fastest object database”
• Cross-platform

261. InterSystems Cache
• Commercial
• “World’s fastest object database”
• Cross-platform
• Persistence of multidimensional arrays

262. InterSystems Cache
• Commercial
• “World’s fastest object database”
• Cross-platform
• Persistence of multidimensional arrays
• Similar to MUMPS/Pick data

263. InterSystems Cache
• Commercial
• “World’s fastest object database”
• Cross-platform
• Persistence of multidimensional arrays
• Similar to MUMPS/Pick data
• Can be embedded in web pages

264. ZODB

265. ZODB
• Open source (Python, Zope license)

266. ZODB
• Open source (Python, Zope license)
• “Seamless object persistence”

267. ZODB
• Open source (Python, Zope license)
• “Seamless object persistence”
• Transactions, MVCC

268. ZODB
• Open source (Python, Zope license)
• “Seamless object persistence”
• Transactions, MVCC
• Scaling across a network

269. ZODB
• Open source (Python, Zope license)
• “Seamless object persistence”
• Transactions, MVCC
• Scaling across a network
• Widely used

270. ZODB
• Open source (Python, Zope license)
• “Seamless object persistence”
• Transactions, MVCC
• Scaling across a network
• Widely used
• Zope Replication Services (commercial)

271. GemStone/S

272. GemStone/S
• Commercial (free license for small apps)

273. GemStone/S
• Commercial (free license for small apps)
• Smalltalk objects just “persist”

274. GemStone/S
• Commercial (free license for small apps)
• Smalltalk objects just “persist”
• Includes Java interface

275. GemStone/S
• Commercial (free license for small apps)
• Smalltalk objects just “persist”
• Includes Java interface
• Automatic and/or guided class upgrades

276. GemStone/S
• Commercial (free license for small apps)
• Smalltalk objects just “persist”
• Includes Java interface
• Automatic and/or guided class upgrades
• Horizontally scaleable

277. GemStone/S
• Commercial (free license for small apps)
• Smalltalk objects just “persist”
• Includes Java interface
• Automatic and/or guided class upgrades
• Horizontally scaleable
• OOCL manages 40% of overseas traffic

278. GemStone/S
• Commercial (free license for small apps)
• Smalltalk objects just “persist”
• Includes Java interface
• Automatic and/or guided class upgrades
• Horizontally scaleable
• OOCL manages 40% of overseas traffic
• JPM’s Kapital created the financial crisis :)

279. GemStone/S
• Commercial (free license for small apps)
• Smalltalk objects just “persist”
• Includes Java interface
• Automatic and/or guided class upgrades
• Horizontally scaleable
• OOCL manages 40% of overseas traffic
• JPM’s Kapital created the financial crisis :)
• Integrates with Seaside

280. GemStone/S
• Commercial (free license for small apps)
• Smalltalk objects just “persist”
• Includes Java interface
• Automatic and/or guided class upgrades
• Horizontally scaleable
• OOCL manages 40% of overseas traffic
• JPM’s Kapital created the financial crisis :)
• Integrates with Seaside
• Web apps with transparent persistence

281. Magma

282. Magma
• Open source (Squeak Smalltalk, MIT)

283. Magma
• Open source (Squeak Smalltalk, MIT)
• Transparent Smalltalk object persistence

284. Magma
• Open source (Squeak Smalltalk, MIT)
• Transparent Smalltalk object persistence
• “Free GemStone/S”

285. Magma
• Open source (Squeak Smalltalk, MIT)
• Transparent Smalltalk object persistence
• “Free GemStone/S”
• Client-server model

286. Magma
• Open source (Squeak Smalltalk, MIT)
• Transparent Smalltalk object persistence
• “Free GemStone/S”
• Client-server model
• HA mode (multiple slaves ready for master)

287. Magma
• Open source (Squeak Smalltalk, MIT)
• Transparent Smalltalk object persistence
• “Free GemStone/S”
• Client-server model
• HA mode (multiple slaves ready for master)
• Transaction-based (commit/rollback)

288. Magma
• Open source (Squeak Smalltalk, MIT)
• Transparent Smalltalk object persistence
• “Free GemStone/S”
• Client-server model
• HA mode (multiple slaves ready for master)
• Transaction-based (commit/rollback)
• Works nicely with Seaside

289. In summary

290. In summary
• Lots of ways to not use SQL

291. In summary
• Lots of ways to not use SQL
• Many open source

292. In summary
• Lots of ways to not use SQL
• Many open source
• Many commercially supported

293. In summary
• Lots of ways to not use SQL
• Many open source
• Many commercially supported
• Don’t assume you need an ORM!

294. How to contact me

295. How to contact me
• Email: merlyn@stonehenge.com

296. How to contact me
• Email: merlyn@stonehenge.com
• Twitter: @merlyn

297. How to contact me
• Email: merlyn@stonehenge.com
• Twitter: @merlyn
• Website: www.stonehenge.com

298. How to contact me
• Email: merlyn@stonehenge.com
• Twitter: @merlyn
• Website: www.stonehenge.com
• Phone: +1 503 777 0095