In this blog post, I’m going to explain how you can make use of the Micronaut framework to organize your project code in such a way that you can externalize and modularize some of your @Beans. These beans can be used as “common” and can be shared between several projects.
I'm in the process of building an #activitypub implementation using #java and #micronaut.
I'm considering options to make the platform "pluggable". The plan is to use something like SPI to load plugins from JAR files, allowing features to be added to customize the platform for individual needs.
Off the top of my head I'm thinking things like custom APIs or storage back-ends to do things which won't be included a (completely theoretical) core distribution.