README

What is this repository for?

• Src code and issues regarding jactor-rises

This project is consisted as three microsevices and where one service is responsible for the persistencde, one for the business logic, and one for the user interface.

The only hard dependencies between jactor modules are:

graph TD;
    jactor.rises.commons-->jactor.rises.facade;
    jactor.rises.commons-->jactor.rises.persistence.orm;
    jactor.rises.commons-->jactor.rises.web;

Set up

• spring-boot applications are created when building (mvn install)
  • jactor-persistence-orm which is a standalone rest application which handles the persistence on a database using an object relational model and spring-data-jpa
  • jactor-facade is a rest applications which is the business logic of jactor.
  • jactor-web which is a web application on apache tomcat
• these applications can run side by side to get a full working web-application (using mvn spring-boot:run on each application)
• jactor-persistence-orm is using h2 (in-memory database), and is not finite
• after started jactor-web, point a browser to http://localhost:8080/jactor-web/

Disclaimer

These applications are not 100% finished, but created for my own learning. That is to say:

• Blogs are only persisted in jactor-persistence-orm and only have an integration test of the rest api that verifies actual interactions.
• GuestBooks have interactions from jactor-model and are tested with an integration test, but lack interactions from jactor-web.
• User (with Person and Address) is fully integrated with communications from jactor-web, which use jactor-persistence-orm (through jactor-facade).
  • Note! Not all services for a User on jactor-persistence-orm is used.

Persistence in jactor-persistence-orm is not satisfactory dealing with identifications. There is therefore an issue (help wanted) created for solving a potential "buggy" solution.

Architecture Summary

There are three microservices in this architecture which all handles all of the technical infrastructure needed for performing the business logic in jactor:

• jactor-web handles all user interaction and use microservice jactor-facade
• jactor-facade is the microservice with the business logic and will use jactor-persostence-orm
• jactor-persistence-orm handles persistence of the data

Why

This is my "sandbox" which I use to learn various aspects of java programming. This repository contains code that is evolved from about the year 2004, going through version control systems as CSV, Subversion, and now Git...

Some technologies used on jactor-rises

• spring framwork 5.x
• spring-boot 2.x
• hibernate 5.x
• h2
• junit 5.x
• assertj
• mockito
• thymeleaf