Lens / Polyglot Systems Lab — Cross-Runtime Service Architecture

Engineering decisions

Decision

Polyglot without accidental platform sprawl

Proposed

Decision

Compatibility across independent release trains

Proposed

Engineering practices

• Common service-level signals — Latency, traffic, errors and saturation need comparable semantics across every runtime.

• Health is a contract — Liveness, readiness and graceful shutdown behavior must be explicit before orchestration can act safely.

• Design failure boundaries deliberately — Asynchronous boundaries, timeouts, retries and idempotency should be chosen based on failure modes rather than language defaults.

• One release policy, many toolchains — Different build systems do not require different standards for quality, artifact identity or rollback.

• Compatibility checks in CI — Breaking a consumer should fail before deployment, not after a cross-service incident.