SMEF Coding Conventions
This is a set of guidelines for the brave SMEF developer that recommend architectural style, practices, and methods to be applied to all SMEF modules and microservices.
- There SHOULD be one container per service
- There SHOULD be one service per container
- Services MUST NOT know each other
- Services SHOULD communicate via message broker
- Service interfaces SHOULD be RESTful
- All APIs MUST be designed to be externalizable
- Data and functionality MUST be encapsulated in services
- Data or functionality of a service MUST be accessed by calling its API
- Service names MUST adhere to the pattern
smef-<module>-<name>, e.g. smef-base-eventreceiver