I found beans in my application鈥檚 bytecode that no class in the project declares. In part 3 of this ArC deep dive, I show how extensions create beans from configuration, why Quarkus doesn鈥檛 run Portable Extensions and how a Quarkus extension works inside.
A constructor that runs twice, an interceptor that works even on internal calls and a bean that doesn鈥檛 even exist at runtime. In part 2 of this ArC deep dive, I show what the Quarkus build changes in application code.
I opened the bytecode Quarkus generates for CDI to see what the container does before the application starts. Part one of a deep dive into ArC with real experiments: discovery, validation and a create() that is just a new.
There is a plugin system hiding inside the JDK that most developers never use on purpose. Java SPI (ServiceLoader) lets you add behavior without touching the code that consumes it. I show it with real code from my NES emulator, kill the fragile META-INF file with Google AutoService, cover the modern JPMS variant, and finish with how Quarkus does the same idea at build time.
Understand how Quarkus reinvented Dependency Injection with ArC: zero runtime reflection, instant startup, and flexible configuration.