Posts Tagged ‘relational’

Caught a fascinating .NET Rocks podcast this morning discussing MongoDB, a NON-relational dbms. Kind of like honest politicians, the possibility of such a thing is theoretically possible but not something you expect to ever actually see. I’m still not sure I have my head wrapped around how to best use it, but it’s hard to argue with the (claimed) vastly improved performance and scalability over traditional RDBMSes!

Interesting little sidenote, apparently the original paper that described the relational database model was published 40 years ago, maybe it is time to look at more advanced approaches…

Combining the best features of document databases, key-value stores, and RDBMSes.

MongoDB (from “humongous”) is a scalable, high-performance, open source, schema-free, document-oriented database. Written in C++, MongoDB features:

* Document-oriented storage (the simplicity and power of JSON-like data schemas)

* Dynamic queries

* Full index support, extending to inner-objects and embedded arrays

* Query profiling

* Fast, in-place updates

* Efficient storage of binary data large objects (e.g. photos and videos)

* Replication and fail-over support

* Auto-sharding for cloud-level scalability

* MapReduce for complex aggregation

* Commercial Support, Hosting, and Consulting

MongoDB bridges the gap between key-value stores (which are fast and highly scalable) and traditional RDBMS systems (which provide structured schemas and powerful queries).

via Home – MongoDB – 10gen Confluence.

Read Full Post »

Interesting if somewhat scathing discussion of using the Entity Framework for n-tier applications from the developers/designers of the next version of the Entity Framework. The feedback has inspired me to look at nHibernate again, and makes me wonder if the Entity Framework is really as safe a bet as one would assume Microsoft’s implementation of a technology would be.

The first version of Entity Framework provides convenient ways to load, manipulate and persist objects and relationships. As with many other O/RMs, Entity Framework has a state manager that tracks every change made. Existing objects are typically loaded first from the database, later modified, and finally the changes are saved back to the store.

Another feature, full graph serialization, makes it very easy for developers to ship around object graphs representing snapshots of the current state of the world, across execution boundaries.

The next version of Entity Framework will also support Persistence Ignorance. Therefore object graphs can now be made of POCO instances, which WCF now also supports.

Nonetheless, there is a task that belongs in any N-Tier application that still requires a great amount of work for developers using EF: decoding messages that represent state changes performed by the client, meant to be processed or persisted by the service.

via Entity Framework Design : N-Tier Improvements for Entity Framework.

Read Full Post »