NouchDB

KO | EN

gitlite — search

#python #ai #typescript #golang #go #macos #nodejs #java #awesome #cli #vue #awesome-list #security #openai

(★ 13)

Embeddable .NET immutable noSQL database that will replicate with CouchDB

NouchDB Latest Version Download

Download Latest Version (.zip)

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

# NouchDB

Embedded .NET NoSql datastore that will synchronise with CouchDB server (TODO: other stores such as MongoDB/Redis).

* Immutable embedded fast JSON datastore
* Based upon the superfast levelDB 
* Master -> Slave replication with a CouchDB server
* MVCC - multiversion concurrency control - each update causes a new record commit. No data is lost we just keep track  
  of the latest revision
* Atomic commit support 
* Supports batch operations
* Simple POCO class persistance model

##Eventual consistency/Offline operation/Master-Slave synchronisation

This project aims to build high performance no-sql immutable JSON database that can be embedded locally within .NET/mono projects.
The master-slave MVCC replication model guarantees eventual data consistency. This is handy if you would like a DB
to continue operating with a local database while a network connection to a remote master database is offline 
and then automatically synchronise once the master database becomes available once more.

![Image of NouchDB](https://docs.google.com/a/kirosoft.co.uk/drawings/d/szsQ3jNOUSQQ1g1blxzTeAw/image?w=657&h=460&rev=228&ac=1)

V0.1 - Limitations

* it is an early alpha so most things have not been fully tested and many probably desireable features are missing
* Currently only master-slave replication is supported.
* The master-slave replication model will basically prioritise server data over any local data.
* Although it is planned to supported nested conflicting revisions - this is currently not fully implemented (see the Node class)

##Currently Supported features:

Data commits from the client are written directly to the remote DB instance and then the localDB is updated
locally via replication. So, in this model the server is the master and many slaves remain consistent with the server
data (as required). Locally committed data is currently lost when writtem locally (no slave -> master replication), 
but the master server can be updated via the couchdb http api.

##Local database commit example

```
NouchDB.NouchDB nouchDB = new NouchDB.NouchDB("fred");

var customer = new Customer { name = "Joe Bloggs", age = 31 };

string input = customer.ToJson();
nouchDB.PutDoc("doc_id1", input);
string output = nouchDB.GetDoc("doc_id1");
Assert.AreEqual(input, output);

string res = nouchDB.Info();

var customer2 = new Customer { name = "Fred", age = 55 };
input = customer2.ToJson();
nouchDB.PutDoc("doc_id1", input);
output = nouchDB.GetDoc("doc_id1");
Assert.AreEqual(input, output);

long[] obj = nouchDB.Info().FromJson<long[]>() ;
Assert.AreEqual(1, obj[0]); // 1 doc
Assert.AreEqual(2, obj[1]); // 2 sequences
```            
            
## Replication with remote server example (local database name is "fred", remote is stars)

```
 NouchDB.NouchDB nouchDB = new NouchDB.NouchDB("fred");

Debug.WriteLine("Documents synchronised: "+Convert.ToString(nouchDB.ReplicateWith("http://127.0.0.1:5984","stars")));
Debug.WriteLine("Documents synchronised: " + Convert.ToString(nouchDB.ReplicateWith("http://127.0.0.1:5984", "stars")));
Debug.WriteLine("Documents synchronised: " + Convert.ToString(nouchDB.ReplicateWith("http://127.0.0.1:5984", "stars",true)));
Debug.WriteLine("Documents synchronised: " + Convert.ToString(nouchDB.ReplicateWith("http://127.0.0.1:5984", "stars")));
//Debug.WriteLine(nouchDB.AllDocs());

```

NouchDB

NouchDB Latest Version Download

Today's picks

Was this content helpful?

Recent Feedback

NouchDB

NouchDB Latest Version Download

Today's picks

Was this content helpful?

Recent Feedback

Download README