...
- Complying with these requirements would be the perfect state, it might be required by real world circumstances to (temporarily) not comply with these requirements
- The registry and traefik microservices serve special roles in the system, they should abide to all the requirements unless deemed to be contrary to their functions.
- Origin: The microservice that is the origin of an object, that stores the basic information of this object.
- Examples: Member's origin is core.
- Internal/External object: When referring to an object from a microservice's viewpoint it is considered an internal object when the viewpoint (microservice) is the origin (microservice), if the viewpoint is not the origin it is considered an external object.
- Example: From the core microservice's viewpoint a Member object is internal, an Event object is external.
- External roles: A role defined by an other microservice, likely unkown to the origin microservice
- Example: Adding a 'trainer' role to a member
Requirements
# | Title | User Story | Importance | Notes |
---|---|---|---|---|
1 | Standard API | A microservice should abide the rules for the standardized API | Must have |
|
2 | Microservice Communication | A microservice should abide to the standardized communication protocol | Must have | |
3 | Standard Object and Data Model | A microservice should abide the rules for the standardized Object and Data Model | Must have | |
4 | Standard Permissions | A microservice should abide the rules of the standardized permission system | Must have |
...