DZone - Introducing DeNSo DB - A New NoSQL Database written in C# for a .Net Environment
"DeNSo DB is provided in its entirety on Github, where you can get a description of its usage, features and theory. The github site has yet to be really fleshed out, and I'm sure readers would be particularly interested in seeing some answers to the question at the bottom: Why should I use it? Maybe you can start formulating your own opinion on that matter by taking a look at this brief summary of what exactly DeNSo DB is.
Right now, DeNSo DB is contending with a few well-established NoSQL databases like MongoDB, RavenDB, and HBase, each of which cater to specific usage. HBase, for example, is a Hadoop database, so it works well with processing Big Data. DeNSoDB currently has a few usages described on the github page:
..."
DeNSo DB
DensoDB is a new NoSQL document database. Written for .Net environment in c# language.
It's simple, fast and reliable.
You can use it in three different ways:
-
InProcess: No need of service installation and communication protocol. The fastest way to use it. You have direct access to the DataBase memory and you can manipulate objects and data in a very fast way.
-
As a Service: Installed as Windows Service, it can be used as a network document store.You can use rest service or wcf service to access it. It's not different from the previuos way to use it but you have a networking protocol and so it's not fast as the previous one.
-
On a Mesh: mixing the previous two usage mode with a P2P mesh network, it can be easily syncronizable with other mesh nodes. It gives you the power of a distributed scalable fast database, in a server or server-less environment.
You can use it as a database for a stand alone application or in a mesh to share data in a social application. The P2P protocol for your application and syncronization rules will be transparet for you, and you'll be able to develop all yor application as it's stand-alone and connected only to a local DB.
Features
- Journaled
- Built using Command Query Responsibility Segregation pattern in mind.
- Store data as Bson-like Documents.
- Accessible via Rest
- Accessible via WCF
- Peer to peer syncronization and event propagation enabled.
- Pluggable via Server Plugin.
- Use Linq syntax for queries.
The Theory
A document database is a Database where data are stored as they are. Usually there is no need to normalize or change their structure, so it's optimal for domain driven design, because you'll not need to think about how to persist your domain.
A document is stored in BSon-like format A document is self contained, and all you needed to understand it's information are in the document itself. So you will not need additional query to understand foreign key or lookup table datas.
You can have collections of document. Collection are not tables, you can think to collections as sets of documents, categorized in the same way. A collection is schema-free and you can store different kind of documents in the same collection.
Every document in every collection is classified using a Unique Identifier. The DB will use the UID to store and to access every document directly.
You can store your data in DeNSo using a Bson document or, more easly you can store your entities in DeNSo.
DeNSo has a Bson De/Serializer able to traduce virtually every entity in a BSon Document and vice-versa." [GD: readme.md leached in full]
I've yet to jump on the NoSQL boat, but have been thinking about it for a couple projects and like that this one is OSS and written in C# (not that I'm saying the others aren't, just that the C# caught my eye...)
Posts
