Compatibility

JDK matrix

Newer JDKs (22, 23, …) are tested but not officially declared “supported” until they have reached at least one quarterly maintenance release.

Runtime environments

DDI is plain Java — there is no servlet, no container, no agent. It works wherever the JDK works:

• Stand-alone JVM — CLI tools, batch jobs, daemons.
• AWS Lambda / Cloud Functions — bootstrap is a single method call, so cold-start cost is the classpath scan, nothing more.
• Vaadin Flow — used in production with Vaadin since the V8 era.
• JavaFX / Swing desktop — same pattern, injection happens before the UI builds.
• JUnit 5 tests — see the JUnit 5 tutorial.

What DDI does not require

• No Jakarta EE / CDI container.
• No Spring ApplicationContext.
• No annotation processor — DDI uses reflections8 at runtime.
• No XML, no YAML, no META-INF/services (though you can use those alongside DDI if you want).

What DDI does depend on

• javax.annotation:javax.annotation-api — for @PostConstruct.
• com.google.code.gson:gson — used internally for diagnostics.
• net.oneandone.reflections8:reflections8 — classpath scanning.
• com.svenruppert:core and com.svenruppert:functional-reactive — the companion libraries (see frp.svenruppert.com).

Java Platform Module System

DDI runs on the classpath today. A proper module-info.java is on the roadmap.