Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Introducing DeNSo DB - A New NoSQL Database written in C# for a .Net Environment

DZone's Guide to

Introducing DeNSo DB - A New NoSQL Database written in C# for a .Net Environment

· Database Zone ·
Free Resource

Running out of memory? Learn how Redis Enterprise enables large dataset analysis with the highest throughput and lowest latency while reducing costs over 75%! 

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:

  • InProcess offers direct access to database memory, enabliing quick manipulation of objects/data.
  • Install the database as a Windows Service, allowing the DB to be a network document store (you can use REST service or WCF service for access)
  • Mix the preceding options to create a mesh with a P2P mesh network, giving you "the power of a distributed scalable fast database"

 Currently, DeNSo DB is journaled and built with a Command Query Responsibility Segregation pattern in mind.  It will be interesting to see if a github-based NoSQL project will get adopted by NoSQL enthusiats. Give it a try and let us know about your experience below.  

 

Running out of memory? Never run out of memory with Redis Enterprise databaseStart your free trial today.

Topics:

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}