Engineering for Long-Term Reliability
Healthcare integration systems need to keep working for years, often decades. Our responsibility is to make that possible.
We've rebuilt our licensing infrastructure around a simple principle: the easier a system is to understand, maintain, and recover, the more dependable it can be.
Good engineering isn't always about adding more technology. Often, it's about removing unnecessary complexity.
Simplifying Our Licensing Infrastructure
Our licensing infrastructure supports both Iguana and Chameleon. These are mature products that customers depend on to keep important systems running.
Over time, the licensing components had accumulated unnecessary dependencies and complexity. We decided to rebuild the infrastructure using simpler components that we could understand, maintain, and recover independently.
The result is a much smaller system with fewer moving parts.
Redundancy Without Unnecessary Complexity
Our licensing service runs on two independent servers hosted by separate infrastructure providers.
The servers use a lightweight Git-based backend to maintain licensing records. This gives us a straightforward way to replicate data, track changes, and recover the system without introducing a complicated database infrastructure.
We deliberately chose established, widely understood technologies rather than building a complex distributed system.
The objective is simple: reduce the number of things that can go wrong and make failures easier to recover from.
Servers as Cattle, Not Pets
One of the most important improvements is that our servers are now reproducible.
Rather than maintaining individual servers that gradually accumulate configuration changes, we use standardized scripts to build and configure them from scratch.
These scripts install the necessary software, configure the services, and apply our security settings consistently.
A new licensing server can be provisioned in approximately five minutes.
This approach has several advantages:
- Failed servers can be replaced quickly.
- Security configurations are consistent and repeatable.
- Software updates can be tested on freshly provisioned systems.
- We avoid undocumented configuration changes.
- The infrastructure is easier for a small engineering team to maintain.
Instead of depending on the history of a particular server, we depend on a reproducible process.
Reducing Dependencies
Software dependencies are a long-term maintenance responsibility.
Every additional library introduces code that must be understood, updated, secured, and supported. Over decades, these dependencies can become a significant burden.
As part of this work, we've simplified the licensing components for Iguana and Chameleon, removing dependencies that were not necessary for their functionality.
This makes the software easier to build, test, and maintain across different platforms.
Our philosophy is to use third-party software where it provides clear value, while keeping the core of our products as independent and understandable as possible.
Security Through Simplicity
Security is not just about adding more layers of technology. It is also about reducing the amount of software and configuration that needs to be protected.
Our new infrastructure uses minimal server installations, automated configuration, and a small number of well-understood services.
By making server provisioning repeatable, we can apply security improvements consistently rather than relying on manual changes to individual machines.
We also reduce our dependence on any single infrastructure provider.
No system can be guaranteed immune to failure or attack. Our goal is to make the infrastructure easier to inspect, secure, replace, and recover.
Supporting Existing Customers
The purpose of this engineering work is not to introduce new technology for its own sake.
It is to ensure that customers can continue using the software they have already invested in.
Healthcare organizations often maintain integrations for many years. Replacing working interfaces can be expensive, disruptive, and unnecessary.
We believe that maintaining compatibility, reducing technical debt, and keeping existing systems reliable are valuable engineering investments.
Our rebuilt licensing infrastructure is one practical example of that commitment.
Engineering for the Long Term
Technology changes constantly, but the needs of our customers are remarkably consistent.
They need their integrations to work today, tomorrow, and years into the future.
That requires software that can be understood, maintained, rebuilt, and supported by the people responsible for it.
Our focus is straightforward: preserve what works, simplify what has become unnecessarily complicated, and make our products easier to maintain for the long term.
That's the engineering philosophy guiding our continued work on Iguana and Chameleon.