#InterSystems IRIS for Health

My team is trying to decide on the best Git strategy for a group of related but separate projects/environments.

One side prefers one repo per project/environment/namespace for cleaner separation. The other side prefers one repo with multiple project folders so shared code and releases are easier to manage in one place.

The challenge is that these projects are separate enough that boundaries matter but related enough that some utilities and common logic may need to be reused. We also want the setup to be easy for developers to understand and not become a deployment nightmare later.

Hi community,

I've been working on a side project that I'd love to get some eyes on: a ground-up rebuild of the classic IRIS Production Monitor using a modern web stack. The existing ZEN/CSP-based portal does the job, but I wanted to explore what a contemporary, real-time version of it could look like.

What it is

A standalone Angular web application that connects to any Interoperability-enabled IRIS namespace and gives you a live view of your production — services, processes, operations, queues, event log, and message traffic — all in one screen.