How lapissea/jdatablockfs works
Major components (modules)
• Core Library (jdatablockfs.core, corresponding in the tree to “jdbfs-core”): Contains the bulk of the storage engine. This includes the memory management, type engine, serialization logic, IO interfaces (such as MemoryData and IOFileData), and core interfaces (Cluster, IOInstance, IOList, IOMap). It is light–weight and designed for efficient in–memory and file–based operations.
• Tools (jdatablockfs.tools, corresponding to “jdbfs-tools”): Optional visual debugging tools, logging interfaces, IPC/visual inspection utilities (e.g., “DisplayHost”, “GraphRenderer”, “DrawFont”). These have extra dependencies (like gson, lwjgl, etc.) and serve mainly for runtime monitoring and debugging.
• Run/Examples (jdatablockfs.run, corresponding to “jdbfs-run”): Houses example usage, realistic integration cases, tests, and benchmarks. Its purpose is to demonstrate and sanity–check the design.
• Jorth: An independent module that focuses on compiling streams of text into bytecode at runtime. Although it’s part of the overall project tree, it is designed as an independent library and is not meant for general use outside internal scenarios.
• Fuzzer (and possibly other demo modules in “demos” such as Photos and World): Modules aimed at testing the robustness of the code (fuzz–testing) and graphical/demo examples.
How the components interact
• Fuzzer and demos (Photos, World) can be positioned as auxiliary components that either test (Fuzzer) or demonstrate (Photos, World) the functionalities in Core (as well as possibly Tools).
Architectural patterns and design principles
• Modular design: Each module is a separate Maven project (as indicated by the pom.xml files), so they are loosely coupled via clearly defined exported APIs.
• Layer separation: Core functionality is separated from optional debugging/visualization features (Tools) and consumer examples (Run). This separation makes it easier to understand dependencies at a glance.
• Custom memory and IO layers: Specifically showing components like MemoryData, IOInterface, and the concept of IOInstance that are central to how the library abstracts storage beyond traditional databases.
• Clear labels for each component (e.g., “Core Engine – Memory Management, Serialization, Type Engine”, “Tools – Visual Debugging, Logging”, “Run – Examples, Benchmarks”, “Jorth – Runtime Bytecode Compiler”).