The document discusses NoSQL databases and describes db4o. It notes that NoSQL databases emerged to address scalability issues with relational databases as data volumes increased. Db4o is described as a powerful yet simple embedded object database that is faster than Hibernate and MySQL for non-trivial use cases. Db4o provides transparent persistence with minimal resource usage and easy implementation across platforms.

1. noSql na prática: db4o
Fábio Medeiros Faria
fabiomedeirosf@yahoo.com.br
www.serjava.blogspot.com

2. noSql?
• O que é? not only Sql
• 1998
• Propósito

3. e o modelo relacional?
• Década de 70
• 4 décadas
• século XX;

4. e o modelo relacional?
• restrições de integridade
• primary key
• foreign key
• normalização

5. e o modelo relacional?
• Limitações:
• volume dados x performance
• usuários versus performance
• sharding

6. ...noSql
• motivação: escalabilidade
• iniciativa: BigTable Google 2004
• Dynamo - Amazon 2007
• Cassandra - Facebook 2008
• Twitter: mysql --> Cassandra
• CouchDB - Apache (MapReduce)
• MongoDB 2009

7. db4o
“the most powerful and yet simple to use
database on the planet”
• open source
• eliminates time consuming and tedious
mapping code
• development process to focus on the
business logic
• embeddable

8. db4o
“the most powerful and yet simple to use
database on the planet”
• PolePosition, shows the db4o 8.0 release to be up to 100 times faster than
Hibernate and MySQL for non-trivial use cases
• Native to Java and .net
• Unique programming library (jar/dll)
• Transparent Persistence

9. db4o
“the most powerful and yet simple to use
database on the planet”
• Minimal consumption of resources
• Easy implementation
• Portable: wide portability “state-of-the-
art”debugging tools
• Reliable: ACID properties:
• ObjectContainer class: commit()
rollback()

10. db4o

11. db4o

12. db4o

13. db4o Customer Success

14. db4o Customer Success

15. db4o benchmarks

16. db4o benchmarks

17. db4o benchmarks