Technology Bricks Workflow Sample Clauses

Technology Bricks Workflow. The diagram above describes the core module groups and interactions of these technology bricks within the CPN platform. In the diagram, we are referring to families of modules. Thus, for the sake of simplicity we are not including every individual module that will be developed. This will be covered during the further design of the architecture and the full definition of components. All calls to the CPN platform will be directed to the API gateway. The API gateway is responsible for the delegation of these calls to the related modules, based on the defined workflow. A message queue will implement a pub/sub protocol to enable modules to fetch and analyse content. For convenience, the synchronous communication between the modules has been represented directly, although in reality, as described in section 3.4, this kind of communication is implemented through an orchestrator. One of the goals is to avoid centralized DBs. Therefore, all modules follow a Microservices approach and store data internally in their own repository of choice. Producers will use the Cute4LE module for pushing content to the platform. The content will be published to a message queue. Before pushing content, producers will also access the Reward Framework in order specify the contracts (e.g. cost per access) that apply to a given content and that producers and distributors have to comply. The web application and the recommender module will also interact with the Reward Framework to provide information on how contents are distributed. The information, published on a distributed ledger for transparent accountability, will allow the Reward Framework to rewarded producers according to the selected contract.