M3 Scenario (Roadmap)

[miwurster]

• 1. Scenario (Multiple Instance Missing)
• 2. Scenario (MIssing)
• Evaluate if MICO can deploy https://github.com/microservices-demo

---

• Team to decide on Wiki/Docs tooling
• Validate and evaluate FaaS platforms/frameworks for usage in M3 (OpenFaaS)
• Gather knowledge to decide implementation strategy for composition patterns (decision pending)
• Prepare MICO setup: setup Kafka
• Prepare MICO setup: setup FaaS platform (OpenFaaS)
• Decide which patterns are implemented specifically (complex patterns) (PO decision pending)
• Implement a generic framework for custom logic patterns (e.g., transformer, splitter, et al.)
  • Generic component is able to work with Kafka layer
  • Custom logic is provided as a function (any lang)
  • Evaluate how to map function with an instance of a generic component
• Working example based on Scenario 1 (having manual steps is okay)
  • M1 - Transform (f) - M2
  • M1 uses a simple message generator
  • M2 simply shows arrived messages in a webpage
  • Transform function must be manually uploaded to OpenFaaS
  • MICO application having M1, M2, and the Generic Comp (with a property that links to the OpenFaaS func - the property may be an env variable that needs to be entered by the user)
  • M1, M2, and Generic Comp service expose a Kafka-aware MicoInterface
• Evaluate MICO domain model in order to represent composition patterns
• Automated setup of scenario 1 with MICO
• Implement OpenFaaS functions:
  • Splitter
  • Content Enricher
  • Content Filter
• Messaging-to-HTTP-adapter:

---

• Extract service network topology into reusable entities (idea by Fabian)
• Highlight topics on message activity in UI (idea by Dominik)
• Routing based on service names, not based on topic names