Investigate/decide/plan asynchronous version of the GMapi

ATTX-project / graph-component

Graph Manager component that handles state of the internal graph/data.

0 stars 0 forks source link

Investigate/decide/plan asynchronous version of the GMapi #32

Closed jkesanie closed 7 years ago

jkesanie commented 7 years ago

Description

DoD

Documentation

Testing

Peer-review

jkesanie commented 7 years ago

We have decided to move that burden from GM-api by introducing a MessageBroker to the stack. Initial resources:

https://github.com/ATTX-project/ATTX-project.github.io/blob/dev/attx_project/MessageBroker.md
https://github.com/ATTX-project/ATTX-project.github.io/blob/dev/attx_project/images/messaging-request-response.svg
https://github.com/ATTX-project/ATTX-project.github.io/blob/dev/attx_project/images/distribution-workflow-basic.svg
https://github.com/ATTX-project/ATTX-project.github.io/blob/dev/attx_project/MessageBroker-ActiveMQ.md

jkesanie commented 7 years ago

@blankdots @joasilva comments?

blankdots commented 7 years ago

There needs to be some update to the role of GM-API to understand its functions and to see how it integrates with Message Broker and its endpoints - probably in the GM or GM-API documentation Suggestion for followup where we describe the implementation and the messages and how to use ActiveMQ with our stack.