World’s smallest No SQL DatabaseThe Devil Is In The Details
So, what is the point of the code that I have shown here: http://ayende.com/blog/162691/worlds-smallest-no-sql-database
The point was to show where you start, and how easy it is, but all the details that you need to handle along the way. I decided that it would probably make for an interesting blog series about the sort of things that this example exposes.
In particular, I want to talk about:
- I/O
- Memory
- Concurrency
- ACID
- Transactions
- Searching
- Scale up
- Scale out
- Aggregation
- High availability
- Backups
- Monitoring
I might have a few more items along the way, but those are probably the most important ones.
More posts in "World’s smallest No SQL Database" series:
- (16 Aug 2013) Persistent data
- (22 Jul 2013) Persistent transaction logs
- (18 Jul 2013) ACID & Transactions
- (11 Jul 2013) Concurrency
- (10 Jul 2013) Memory
- (08 Jul 2013) The Devil Is In The Details

Comments
Comment preview