Welcome to MICO’s documentation!

Mico is a project for designing, deploying and managing applications consisting of multiple services.

See also

MICO Developer Documentation

Documentation Structure

Contents:

• Mockups
  • Initial sketch of MICO
• Domain Model
  • MicoApplication
  • MicoApplicationJobStatus
  • MicoEnvironmentVariable
  • MicoServiceBackgroundJob
  • KubernetesDeploymentInfo
  • MicoLabel
  • MicoMessage
  • MicoService
  • MicoServiceDependency
  • MicoServiceDeploymentInfo
  • MicoServiceInterface
  • MicoServicePort
  • MicoPortType
  • MicoServiceCrawlingOrigin
  • MicoVersion
  • MicoInterfaceConnection
  • MicoTopic
  • MicoTopicRole
• Database Schema
  • Overview
  • Service
  • DependsOn
  • Service Interface
  • Application
  • Possible Nodes and Relationships
• Messaging
  • CloudEvents
  • Error Report Messages
• REST API
  • Structure Overview
  • Openapi Specification
  • Method Details (specification)
• Setup
  • MICO Setup
  • Azure Kubernetes Service
  • Google Kubernetes Engine
  • Development environment
  • CI/CD Pipeline
  • Kubernetes
• Debugging & Testing
  • Testing
  • Debbuging
  • Postman
• MICO Tutorials
  • How To add a service
  • How To manage a service
  • How To add an application
  • How To manage an application
  • How To create a messaging based application
• Architectural Decision Log
  • 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
  • 22. Configurable Service Dependencies
  • 23. Kafka as Messaging Middleware
  • 24. Function to component mapping
  • 25. FaaS
  • 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
  • Open Decisions
• Glossary