This is the manual for older MicroStream versions (Version < 5.0).

The new documentation (Version >= 5.0) is located at:

Build Configuration

You can find the MicroStream libraries in our Maven repository



or in our P2 Update Site:


These are the different modules that make up MicroStream.




Collection of common utilities. Math, IO, Exceptions, Threads, String operations, and so on.



Hibernate region factory for jcache implementation


Top-level framework for sending and receiving object graphs between Java applications. Only data is transferred, no program code ("bytecode"). The other application may be programmed in any language as long as it adheres to the transmitted communication protocol. Usable directly in the program code of a Java application to communicate with other applications or processes. The concrete form of persistence is left open and delivered via a specific implementation as a plugin. Examples of specific persistent forms are binary data, CSV, XML, Json.


Plugin framework for the top-level framework communication to convert the transferred object graphs to and from binary data.

File system implementations for AWS (S3, DynamoDB).

File system implementations for Azure Cloud (Azure Storage).


Base for all blob store file system implementations.


File system implementation for Oracle Coherence.

filesystem hazelcast

File system implementation for Hazelcast.


Generic file system implementation for JPA / Hibernate.


File system implementation for Apache Kafka.


File system implementation for MongoDB.


File system implementation for Oracle Cloud Services (Object Storage).


File system implementation for Oracle NoSQL.


File system implementation for Redis.


File system implementation for SQL databases.


Base framework to convert a graph of java objects into a persistent form and back. Usable as a common, abstract base for all technologies implementing a specific persistent representation like binary data, CSV, XML or Json.

From a technical point of view, storage as well as serialization is a process that puts a graph of Java instances into a persistent form. The only difference is that network communication serialization discards this persistent form while a database solution preserves it.


Extension of the persistence base framework with a concrete implementation of the persistent form as binary data. This persistent form is superior to all text-based formats in storage and performance needs, making it the preferred method for storage and network serialization.


Specialized type handlers for JDK 8 collection types.


Basic framework to manage a graph of Java data persisted as binary data as a database. Can be used both to implement an embedded database solution (in the same process as the Java application) and a standalone or server-mode database solution (in a separate process). Other forms of persistence than binary data are deliberately not supported because they would not bring any noteworthy advantages but many disadvantages for the task.


Top-level framework for use in a Java application that adds an embedded database solution to its object graphs. Can be used directly in the program code of a Java application to comfortably and efficiently persist its data.


Layer with support for external configuration files (XML, INI) and convenience functionality to create foundations for the embedded storage.


Adapter for low-level storage data externalization. Used by the REST service to adapt to a MicroStream Storage.


Abstract REST client interface, which serves as a Java wrapper for the REST API.

Executable client app with web user interface, which connects to a REST service.


REST client implementation which utilizes Jersey as a webservice framework.


Abstract REST service interface, which uses the REST adapter to access low level storage data.


REST service implementation which utilizes SparkJava and provides REST endpoints.

Dependency Graph

Last updated