This document discusses a Java-based system for managing decision tables and rule editors. It proposes using Javers to provide version control capabilities, Spring Data repositories for data access, and an MD editor interfacing with an MD database. Key business requirements are to track change history, support draft/commit workflows, and handle conflicts during merges across branches. The technology stack suggested includes Java 8, Spring, JPA, and object serialization.

1. Elad Hirsch
FullStack Lead@ IDI
3.12.2017
Java.IL - the Israeli Java Community

2. Full-Stack Dev/Team lead @ IDI

3. MD Editor - Desicion tables

4. MD Editor - Rule Editor

5. Architecture

6. What do we really see

7. Business requirements
• Track changes history
• Draft -> Commit changes
• Diff & Conflict managent
• Support branches and merges

8. Tech Spec
• Java 8 + Spring eco-system
• JPA / ORM specification
• Object Serialization

9. “version-control” like capabilities
The change
“version-control” like capabilities
The change

10. Spring Data
CRUD Repositories
Javers Repo
MD Editor
MD-DB
Architecture

12. Why Javers

13. Why Javers

15. Why Javers

17. What's next – Javers

18. Thank you!
3.12.2017
Java.IL - the Israeli Java Community