Server Types

1. Deployment Server for PROD and DEV
2. RunTime Servers with two types one as API-Server and other as Background Server (queue)

Release

1. DEV: each package it has as SNAPSHOT version with format 1.0.0-SNAPSHOT.{n}
   1. increment n (npm version 1.0.0-SNAPSHOT.1 --workspaces)
   2. take git tag
   3. publish 1.0.0-SNAPSHOT.{n + 1}
2. Fix: 1.0.0

to release from DEV to fix need to cute the SNAPSHOT part from and increment the DEV version for next release

TODO: Add static analysis for code like 'dependency-cruiser'

Deployment

there are Deployment-Repository for deployment on PROD and DEV stages. IN DEV all artifacts deployment contains SNAPSHOT version and on PROD Fix version.

TODO: create deployment scripts for each artifact.

Deployment Pipeline

1. Build
2. Test
3. PROD-DATA to DEV
4. Deploy on DEV
5. wait for input: accept or reject?
6. if accepted then release SNAPSHOT version with tags and deploy on PROD

Architecture

Depends on the server type the artifacts deployed ether behind loadbalancer or not.

Artifacts that need loadbalancer (API-Server)

1. commands
2. readers
3. uploader

Artifacts that deployed without http access or loadbalancer (Background Server)

1. mailer
2. notification
3. resizer

Dependency Injection

base and db are not depends on other modules.