Skip to content

W-JAX Munich 2021: "How to Show Version Histories in Java Application Front-Ends?"

Published on · Updated on · 3 min read
W-JAX logo

Share

Logistics

Conference

W-JAX Munich was a hybrid conference for Java, architecture, and software innovation, held November 8-12, 2021. Most talks were in German.

Talk

My talk was on Tuesday, November 9, 2021, local time.

I put an application that used JaVers into production in May 2021. I had given earlier versions of this talk (which only discussed JaVers) to the London Java Community.

Abstract

German

Anwendungen wie Dropbox und OneDrive speichern alte Versionen von Dateien. Dieser Versionsverlauf zeigt uns dann, wer was wann wie geändert hat. Was wäre, wenn die Frontends unserer Java-Anwendungen auch solche Versionsverläufe hätten? Uns sogar zwei Versionen vergleichen lassen würden? Unsere Anwender fänden das toll, weil sie so wichtige Änderungen selbst finden könnten. Und zufriedene Anwender wenden sich seltener an den Kundendienst!

Wie bekommen wir nun Versionsverläufe in unsere Java-Anwendungen? Wir müssen dafür Versionen im Backend speichern und im Frontend anzeigen. Dieser Vortrag vergleicht vier Möglichkeiten zum Speichern von Versionen: Do-it-Yourself, die Open-Source-Projekte Hibernate Envers und JaVers und kommerzielle Produkte wie Datomic oder Crux.

Im zweiten Teil des Vortrags diskutierte ich meine Erfahrungen mit JaVers in einer Spring-Boot-Anwendung. Diese Anwendung hat ein Web-Frontend (Angular) und native Apps für iOS und Android (Flutter). Mein Ansatz war die Versionierung der DTO für das Frontend. Dadurch konnte ich die Komplexität der Speicherung und Anzeige der Versionen dramatisch verringern. Abschließend hob ich typische Probleme mit JaVers und deren Lösung hervor.

English

Applications like Dropbox and OneDrive keep a version history for files. That history shows who changed what when how. Now, what if Java application front-ends had such version histories? Even let us compare any two versions? Users would love it because they could find important and otherwise invisible changes themselves. And happy users contact support less often!

So, how to add version histories to Java applications? We need to store versions in the back-end and show them in the front-end. This talk compares four ways to store versions: Do-It-Yourself, the open source solutions Hibernate Envers and JaVers, and commercial platforms like Datomic or Crux.

Next, I discuss my experiences with JaVers in a Spring Boot application. It has an Angular web front-end and native apps for iOS and Android (Flutter). I versioned the Data Transfer Objects for the front-end. This dramatically reduced the complexity of storing and showing the changes. Finally, I highlight typical issues with JaVers and how to solve them.

Historical note (as of November 2021): After the talk, attendees could rate it live and leave feedback via Mentimeter. That poll is no longer reachable today.

Historical note (as of November 2021): At the time, I was looking for a new project starting in October 2022, in Milton Keynes, London, or remote.

Slides

The slides are available as a PDF. They’re 7.7 MB:

Download slides (PDF)

Historical note (as of November 2021): Back then, the slides were also available in their original Keynote format with less text and animations; that file is no longer available today.

Additional Talk Information

Here are the four candidates for creating versions:

Getting Started with JaVers

So you want to add an audit log to your application with JaVers yourself? Wonderful! My Getting Started guide can help.

Getting Started with JaVers