NB: This project was initially as a space for experimenting with new ideas
This project supports Certify-d's efforts as an online document certification platform.
What does this project tries to solve?
A high-level architectural overview of the system details how different person/actors, the systems itself, and other (external) systems interact.
All services are for the API project are within this single mono-repo. This project is structured is follows:
- .prow: k8s Prow CI/CD jobs
- api: OpenAPI & gPRC related files
- common: shared pkg's usd by all micro-services
- conf: project wide configuration files
- docs: documentation related files
- scripts: scripts to run for builds, deploys, etc.
- service.upload: micro-service, handling of all file storage operations
- service.user: micro-service, handling of all user operations
- third_party: external 3rd party tools/services
- kratos: user identity & management system, see Ory Kratos
- oathkeeper: identity & access auth proxy, see ory.sh
Each project/micro-service is version independently. For each version, a git tag is created and used. The conversions for all tags are as follows: my_app/v0.0.0
- Certification service, handling of transforming files to stamped 'certified' docs
- Notification service, handling of all notification operations
- Order service, handling of all order operations
- Payment service, handling of all payments operations
Bidding service: handling of outsourcing services to 3rd parties