Prototype a new approach for a CMR development environment manager

[oubiwann]

Important Links:

• Problem Statement
• High-level requirements
• Project Design Goals
• Areas to Explore

Epic features:

• System
  • Add component infrastructure
  • Implement whole-system state management - see Implement whole-system state management #11
  • Add component messaging capability - see Add component messaging capability #4
  • Implement dev-env-only components - IN PROGRESS - see Implement dev-only components #9
• CMR Services
  • Implement service components - IN PROGRESS - see Implement individual CMR service components #8
  • Implement per-service state management - see Implement per-service state management #10
• Monitoring
  • Create fs watcher protocol/API - see Create fs watcher protocol/API #32
  • Add file system watcher component - see Add file system watcher component #38
  • Manage code changes - see Manage code changes #35
  • Support auto-restarting services (optional)
  • Support auto-reloading changed files (optional)
  • Add service monitor (health check) component - IN PROGRESS - see Add health checks component #17
  • Support auto-killing/restarting of services with lost connections (optional)
• Performance
  • Add JMX instrumentation - see Add instrumentation #3
  • Add time-tracking to state management - see Add time-tracking to state management #12