Skip to content
This repository has been archived by the owner on Nov 11, 2020. It is now read-only.

Home

Jump to bottom
ashleyfrieze edited this page Sep 2, 2014 · 2 revisions
  1. MicroNoSql
The aim of this is to provide a simple NoSql data source which can persist Java objects. It is intended for use in-process in lightweight applications where filesystem will be used to store the data.

For the purposes of development and ease of unit testing, it comes with an in-memory version of the storage. This can be used instead of persistence to filesystem in real-world applications where a NoSql-like database is required to share information between threads.

See [Examples]

    1. Motivations
  • Run on small scale hardware
  • Avoid any query language - it's all core Java
  • Lightweight annotation model - very little to declare other than POJOs
  • Optimise for storing/retrieving individual items by key - the most common pattern
  • Store to disk in such a way that front end could be written without server-side processing
    1. Static Content Model Explained
  • If the persistent data is all accessible as static content then the front end could access it without server-side services
  • This allows for very low-overhead applications to be built, with an Apache or Nginx front end serving the data as content
  • The data that's served could even be replicated from a different machine running the editor engine as a Java application
Clone this wiki locally