Arquisoft / Arquisoft/InciManager_i3a

Split in to service | client architecture

Open
#65 0 comments 0 reactions 0 assignees View on GitHub
affects: cd affects: ci affects: code affects: documentation difficulty: medium priority: high type: improvement
Dominant language
Java
Stars
4
Forks
2
PR merge metrics
No merged PRs in 30d

Description

## I'm submitting a...



[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report
[x] Feature request
[ ] Documentation issue or request

## Description

Both client and service are implemented as a monolith instead as a distributed services as the other modules. For that it is needed to split in to two repositories, one for the client and another for the service. Look the following scheme where the whole architecture is described.

![aws-gestusers - new page 1](https://user-images.githubusercontent.com/10364506/38865569-74c8948c-423e-11e8-900e-57069aae022a.png)

You can take as an example the **[agents_service](https://github.com/Arquisoft/Agents_i3a)**.

Contributor guide

Open the contributing guide

Research direction

Review the current InciManager_i3a repository structure and compare it with the linked agents_service example. Determine the boundaries for the client and service, then verify that the architecture is represented as two separate repositories matching the referenced scheme.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
distributed-systems
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.