Data Model

WAL: Write a Log first when a write comitted.

records in the following simple formart:
{name=jack, age=30, payment=500, date=20150728}
{name=michal, age=25, payment=800, date=20150728}
{name=frank, age=25, payment=1200, date=20150729}
{name=jackson, age=45, degree=master, address=somewhere, payment=2000}
......

name, age, payment, date and all these alike are Properties, programmers need no further work to tell Lunarbase which one is the key explicitly. Any Property with its value is a key, and searchable with equal performance.

Log system is first of all we implemented, every command user commits is recorded before execute real database operation:
succeed@ insert: {name=jack, age=30, payment=500, date=20150728};
succeed@ insert: {name=michal, age=25, payment=800, date=20150728};
succeed@ insert: {name=jackson, age=45, degree=master, address=somewhere, payment=2000};

Schema Free, all properties is added on demand. As what the example illustrates, name ,age, payment, date appears when new records inserted. In the future, the comming data may includes new properties like address, school, LunarBase recognizes these, and store them automatically:
property@ name, age, payment, date, degree, favorate......

Remark:
Properties of a Data Application is the very first thing need to be clear when start to design and program in old days. But now, the data types variants much more frequently than before, no one has the capability to know the future category a bunch of data belongs to.

This is what the industry calls ** Scalability** and Flexibility, an advantage of NoSQL database.