A .NET document database interface for relational databases, because in SQL we (still) trust !
How does it work ?
YesSql is a .NET Core document database interface over relational databases which allows you to define documents and indexes using plain old CLR objects. The main difference with document databases is that it uses 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 !
A video about YesSql was recorded and is available here https://www.youtube.com/watch?v=D42eK6CJjF4
Aren't NoSQL databases also about map/reduce ?
YesSql has support for it too. There is a sample 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 sample to ensure it fits your needs. Here is the output on my machine using Microsoft SQL Server 2016:
YesSql Wrote 5,163 documents in 2,157ms: 2.39: docs/ms Queried by full name 100*3 times at 430ms Queried by partial name 100*3 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. Each index is a custom class which has its own table. A reduce index also adds a bridge table in order to map many documents. Internally YesSql communicates with the database server using Dapper.
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 custom serialization libraries and Lucene to store the data might scare some 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.