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