MicroStream version 6 is now available. The new version 6 supports the new Java version 17 and comes with specialized type handlers for Java 17 collections, provides deep copies of object graphs, introduces a new config layer for Spring Boot, and eliminates various bugs.
The upcoming Helidon version 2.4.0 comes with an integration for MicroStream 6. MicroStream will be integrated with both, Helidon MP and Helidon SE. Helidon is a leading framework for developing modern cloud-native microservices with Java. Helidon is open source and mainly developed by Oracle. In comparison to other microservice frameworks, Helidon is the only one that is comprised of two different versions, so-called flavors: Helidon MP and Heldion SE. Helidon also provides a first-class integration for GraalVM native images. At JCON-ONLINE 2021, Dmitry Kornilov, Director of Software Development at Oracle and Project Lead of Helidon, has officially announced that MicroStream has now been integrated with Helidon.
Spring Boot configuration layer
The new MicroStream version comes with a configuration layer for Spring Boot. However, different to the Helidon integration, this is not a full integration with Spring Boot. For example, the integration of MicroStream with Spring Data is not suitable, since MicroStream is not an ORM framework. Nevertheless, this configuration layer should make it Spring Boot users now much more convenient to use MicroStream. Add the dependencies ...
Specialized type handlers for Java 17 collection
With the new MicroStream release, new type handlers are now available, to ensure proper handling of immutable collection types, created with List.of(…) and Set.of(…).
MicroStream 6 introduces a new utility type one.microstream.persistence.binary.util.ObjectCopier to quickly create deep copies of object graphs, which leverages the MicroStream serializer. If the application works in MVC frameworks, the work is often done by getting some data from a data source, modifying it, and then store it back in a data store. This style of work application always works with a copy of the data, which allows to use mutable data only within a single thread. The developer doesn’t have to worry about data synchronization and then store this data in a database transaction. This way of working is very practical, it does not require developers to have knowledge of multithreaded programming and thanks to this it is very widespread. Similar technical work can now be used with MicroStream as well. The ObjectCopier utility can be used elegantly, safely and very simple to create a deep copy of the data, changing it, and to save it back. MicroStream provides 2 options: Deep copy and Shallow copy. Learn more ...
For migrating from version 5, no measures are necessary, for older versions see our migration guide.