Architectural Decision Log

This log lists the architectural decisions for MICO.

• 1. Template
• 2. Use Markdown Architectural Decision Records
• 3. Java Framework
• 4. Performance considerations
• 5. Security considerations
• 6. Monolith as Architectural Style
• 7. Repository Structure Frontend/Backend
• 8. Web-UI Framework
• 9. Database Technology (Relational/Graph)
• 10. Browser Compatibility
• 11. Features first
• 12. REST API Design
• 13. JSON+hal as serialization Format for the API
• 14. Re-use capabilites of Winery Topology Modeler
• 15. Source-to-Image Workflow
• 16. Evaluate Spring Data REST
• 17. Building OCI Images
• 18. Documentation Structure
• 19. Istio vs. Envoy
• 20. Requirements regarding the Composition of Applications
• 21. Architecture for background jobs
  • Java ExecutorService
  • Java CompletableFuture
  • Spring Scheduling
• 22. Configurable Service Dependencies
• 23. Kafka as Messaging Middleware
  • Client subscriptions
  • Client positions
  • Guarantees for message delivery
  • Message delivery modes (how to achive exactly once)
  • Use topics storage for key based data
• 24. Function to component mapping
• 25. FaaS
  • OpenFaaS
  • OpenWhisk
  • Kubeless
  • Knative Serving
• 26. Language for a generic composition pattern implementation
• 27. [WIP] Kafka-faas-connector requirements (aka generic component requirements)
• 28. Implementation of complex EAI-Patterns with FaaS
• 29. Simple Composition Components
  • Generic Component Requirements
  • 717
  • 718

For new ADRs, please use template.md as basis.

See also

More information on MADR is available at https://adr.github.io/madr/.

General information about architectural decision records is available at https://adr.github.io/.

Open Decisions

This section contains open decisions that may not have an ADR yet but are relevant for the project in the (near) future. Each decision should be a list item with a short description.

• Application Graph Editor: Winery Topologymodeler OR custom d3 editor