JaVers is designed as a framework for auditing changes in your object-oriented data.
With JaVers you can easily commit changes performed on your object graph to a specialized repository (called JaversRepository). Then you can browse the detailed change history of a given object in two forms — diffs and snapshots.
The data auditing framework is built on top of the object diff engine, which could be used as a standalone object diff tool for ad-hoc comparison of two object graphs.
All JaVers functions are exposed via a single Facade, the JaVers instance. As you can see, JaVers API is concise and simple.
JaVers object diff is the easiest way to deeply compare two object graphs.
How to use it?
As the result, you get list of atomic Changes. There are several types of Changes: ValueChange, ReferenceChange, ListChange and so on (see the inheritance hierarchy of Change class to get the complete list).
Take a look at diff examples.
is the central part of our data auditing engine.
It tracks every change made on your data (both values and relations) so you can easily identify when the change was made, who made it and what was the value before and after.
How to use it?
Configure and build a JaVers instance (see configuration).
Integrate JaVers with your system by applying the
javers.commit()function in every place where important data (domain objects) are being created and modified by application users.
You don’t need to commit every object. JaVers navigates through the object graph, starting from the object passed to
javers.commit()and deeply compares the whole structure with the previous version stored in JaversRepository. Thanks to this approach, you can commit large structures, like trees, graphs and DDD aggregates with a single
If you are using Spring Data, annotate your Repositories with @JaversSpringDataAuditable and take advantage of the auto-audit aspect.
Once your domain objects are being managed by JaVers, you can query JaversRepository (see JQL examples) for objects change history.
JaVers provides two views on object change history: diffs and snapshots. Use javers.findChanges(JqlQuery) and javers.findSnapshots(JqlQuery) functions to browse the detailed history of a given class, object or property.
Take a look at repository examples.
JaversRepository is designed to be easily implemented for any kind of database.
At the moment we provide MongoDB implementation and
SQL implementation for the folowing dialects: MySQL, PostgreSQL, H2,
Oracle and Microsoft SQL Server.
See repository configuratoin.
If you are using another database, for example Cassandra, you are encouraged to implement the JaversRepository interface and contribute it to JaVers project.
JaVers has a well-designed and customizable JSON serialization and deserialization module, based on
GSON and Java reflection.
Your data are split into chunks (atomic changes) and persisted in a database as JSON
with minimal mapping configuration effort
(see custom JSON serialization).