A .NET document database working on any RDBMS
Switch branches/tags
Nothing to show
Clone or download
Pull request Compare This branch is 261 commits behind sebastienros:master.
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.



A .NET document database using any RDBMS, because in SQL we (still) trust !

How does it work ?

YesSql is a document database which allows you to define documents and indexes using plain old CLR objects. The main difference with other document databases is that it uses NHibernate and any RDBMS to store them, which gives you all the power of SQL databases like transactions, replication, reporting, ... But the main advantage might be that there is no magic involved. It's pure SQL !


Aren't NoSQL databases also about sharding and map/reduce ?

YesSql has support for it too. There is a YesSql.Shards.Demo project in the source code, and you'll see that map/reduce is fully supported by looking at the tests.

Aren't NoSQL databases faster than SQL databases ?

Well, I don't know what fast is, but you can try to run the Performance test to ensure it fits your needs. Here is the output on my machine using Microsoft SQL Server 2008:

YesSql Wrote 5,163 documents in 2,157ms: 2.39: docs/ms

Queried by full name 1003 times at 430ms Queried by partial name 1003 times at 827ms

This performance test is based on one used to compare Redis to RavenDb that you can find here: http://www.servicestack.net/mythz_blog/?p=474

How is the database structured ?

There is a global [Document] table per shard. Then each index has it's own table. In the case of a map/reduce index there is also another table to handle the many-to-many relationships between an indexes and documents.

Dude ! Why another document database ?

I know :/ Well actually I am a big fan of document databases and I am well aware that some like MongoDb and RavenDb are already top-notch ones, but what if you want a free, transactional .NET document database ?

  • MongoDb is not transactional, and some applications can't cope with it. RDBMS on the contrary are all transactional.
  • RavenDb (which I am a big fan of) is not free. Also the fact that it's using Lucene as a storage engine might scare companies which have invested a lot in SQL, trust SQL, and have in-house experts.

So YesSql might be an answer for the developers who face those restrictions. If you don't care about those then please don't spend one more minute on YesSql, it's useless for you.

I am sold, where do I start ?

The documentation is here: https://github.com/sebastienros/yessql/wiki

You can also take a look at the sample apps in the source code.