Inside the Quarkus reactive core, part 3: a Uni is a recipe, not a result
An order that compiles, runs, returns the right confirmation and never writes its audit log. Part three of the series: what a Uni actually is, who subscribes to it in Quarkus, and why Mutiny schedules nothing on its own.