With StreamStore you can take your Java objects and put them into the StreamStore Storage system. Your java objects can be organized as you please. Your objects, are stored in a StreamRecord within a StreamTable. In this way, StreamStore has become a database of your java objects.

The StreamStore BTree subsystem is an enhanced BTree index facility which itself uses the StreamStore Storage subsystem. Your java objects can each be indexed using a BTree.  Having a BTree index for your objects gives you very fast access to those objects.

The StreamStore StreamId is a built in identifier for each StreamRecord in existence.  If you stored one object per StreamRecord then the StreamId is equivalent to an object id.

Once you understand StreamStores, StreamTables, StreamRecords, BTrees and StreamIds you understand the fundamental parts of StreamStore.

For more detailed information consult the StreamStore User's Guide.

The diagram above shows two subsystems: Storage and BTree.  This allows you to take one without the other to build your own custom persistence solution.  Below are some of the ways to use StreamStore:

• For storage and Indexing. This is a standard usage of StreamStore where user objects are placed in storage and are indexed using the BTree.
• Just for storage. If your aim is to store end user java objects but not use the indexing capabilities of the BTree, then just use the Storage subsystem.
• Just for indexing. On the other hand, if you want to use the BTree indexing capabilities but not use the storage system directly, then just use the BTree system.
• For storage and custom indexing. Another usage is to use the storage system for your user data but build your own type of index which you can then persist using storage.
• Due to the flexibility of the StreamStore data model you can store any kind of data in it and build your own custom components on top to suit your application needs.