Messaging Service Description and Assumptions
Description
Allows application components to create, send, receive, and read asynchronous messages.
Boilerplate structure and text below
Much of the page structure and text below this point is boilerplate, copied in from the relevant New Service template. Further work is needed to complete this page.
Assumptions
- This service is expected - at least during its initial conception - to be based on a simple Java Message Service (JMS) model.
Key Concepts
- Especially things that become common sense, and so usually missed by new reviewers
Dependencies
- Note other services that are consumed or that are closely related to this one
Background Documentation
- If we have notes from community design meetings, link to them here.
- If we have relevant sections in Spectrum or another such document, link to them here (or cite section numbers, etc.)
Key Team Members
- (Name(s) of members) is/are the primary tech team member(s) for this service
- Need to identify the community members acting as Domain Experts.