Redux with MongoDB-like API.
Notice that NOT all the features of MongoDB are implemented here, such as multi-index and query operators.
The purpose of reduxdb is to avoid writing almost the same actions and stores again and again in different projects.
A database is generally used for storing related, structured data, with well defined data formats, in an efficient manner for insert, update and/or retrieval (depending on application).
On the other hand, a file system is a more unstructured data store for storing arbitrary, probably unrelated data. The file system is more general, and databases are built on top of the general data storage services provided by file systems.
npm install --save reduxdb
var reduxdb = require("reduxdatabase")
var db = reduxdb.use("test")
db.createCollection("users", {index: "id"})
db.createCollection("teams", {index: "id"})
db.createCollection("books") // using default index `_id`
db.subscribe(function() {
console.log(db.stats())
console.log(db.users.stats())
console.log(db.teams.stats())
console.log(db.books.stats())
})
db.users.insert({id: "1234", name: "wizawu"})
db.users.findOne({name: "wizawu"}).id // 1234
- use(name)
A database is generally used for storing related, structured data, with well defined data formats, in an efficient manner for insert, update and/or retrieval (depending on application).
On the other hand, a file system is a more unstructured data store for storing arbitrary, probably unrelated data. The file system is more general, and databases are built on top of the general data storage services provided by file systems
ReduxDB:
A database is generally used for storing related, structured data, with well defined data formats, in an efficient manner for insert, update and/or retrieval (depending on application).
On the other hand, a file system is a more unstructured data store for storing arbitrary, probably unrelated data. The file system is more general, and databases are built on top of the general data storage services provided by file systems.
-
Parallel First Design Pattern
-
Symntic query: like google/fb
-
normilze, schema, redux, reselect
-
GraphQL: Solves REST problesm for limited fields and offset etc
-
migration for mongo and mysql
-
ES6 from scratch
-
Deserializing on browser: localstorage or redux form. Eg: info related to session user
-
Integrate features one by one
-
Joins/Aggregation between tables/JSON objects
-
lodash
-
Version controlled
-
No separate service in background
-
Speed Test on large record
-
ML data
-
jest testing DB, snapshot testing?