MicroKernel & NodeStore
Download as PPTX, PDF0 likes1,102 views
The MicroKernel provides a remote procedure call interface for accessing a content management system and has two main implementations, while the NodeStore maps the MicroKernel concepts to Java interfaces and provides three main implementations, including the KernelNodeStore which maps to the MicroKernel. Both the MicroKernel and NodeStore are designed to work together to provide a content management system, with the MicroKernel handling the interface and serialization and the NodeStore mapping it to Java and providing different storage backends.
MicroKernel & NodeStore
- 1. MicroKernel & NodeStore two sides of the same coin
- 2. MicroKernel (interface) Designed with remoting and potential non-Java implementations in mind RPC-like, with JSON/P serialization Two main implementations: MongoMK (the new MongoDB-based MK) “H2” MK (old one, to be deprecated)
- 3. NodeStore Mapping of MK concepts to an object- oriented, native Java set of interfaces Omissions: direct journal access, filter rules Extensions: NodeBuilder, NodeStateDiff No serialization, random access possible Three main implementations MemoryNodeStore (for testing, utilities) KernelNodeStore (MK mapping) SegmentNodeStore (the Segment/TarMK)
- 4. MicroKernel (architecture) Key points Basic content tree model MVCC-based revisions Merging of concurrent changes Any implementation a “MicroKernel”, regardless of the specific interface