Quarkus Machina: @BuildSteps for applications

[William Burke]

So, I always thought the @BuildStep pattern in quarkus would be useful in an application.  I needed a break recently and decided to implement this as a Quarkus extension with a different API.  I just have a feeling this might be useful for agentic and other workflow use cases.

It is call Quarkus Machina.  You define @Gears (build steps) and @Machines (what you want to create).  It also works with dynamic input.  All gears are CDI beans of any scope you want.

A bigger description (and code base) is here:

https://github.com/patriot1burke/machina

Don't know if I'll take it further, but just always wanted to create this extension.

Cheers,

Bill

--

Bill Burke

IBM

[George Gastaldi]

Cool, but isn't that similar to David Lloyd's work with https://github.com/quarkus-qlue/qlue?

--
You received this message because you are subscribed to the Google Groups "Quarkus Development mailing list" group.
To unsubscribe from this group and stop receiving emails from it, send an email to quarkus-dev...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/quarkus-dev/CAL%3DE%3DjQprEjcMFUmmA1pz%2BN9x82d7-tk-cGTWOEcr828x-q8zA%40mail.gmail.com.

[William Burke]

LOL!  Cool! 

/delete quarkus-machina

To view this discussion visit https://groups.google.com/d/msgid/quarkus-dev/CAK6y9v04SntjGWFefJqw5TYuv3wYmUt69LHwmCMnN36YYkHaQA%40mail.gmail.com.

--

Bill Burke

IBM

[William Burke]

Actually here's the things I didn't like about Quarkus @BuildStep which I think Qlue inherits too.

* The requirement to extend from Simple/MultiBuild item.  This should be annotation based to allow app devs to have their own hierarchy - @SingletonItem.

* Requirement that items are final classes.  Simply state that producing/consuming only works per class type.

* Checks should be done at build time, i.e. a class is final, no-generics etc...  Having to wait until runtime to find out you've crafted a item or step wrong is just a PITA.

* Primitive types and String can't be consumed/produced

* It is output driven rather than input driven.  i.e. you have to specify the output you want.  I know this is a feature, not a bug, but the flip side:  you have some input and want to see what output is generated is also a useful case.

Honestly, will probably never revisit this project.

--

Bill Burke

IBM