pf4j VS moduliths

I'm working in a spring boot based environment using a setup similar to pf4j where additional JARs can be loaded at will during runtime. Each plugin may implement a set of interfaces which are then dynamically registered in the Applications IoC. The important part is: Each jar is loaded within a separate ClassLoader.

Hi everyone! Recently I've needed to figure out how PF4J library can be used from Clojure, and it was not very straightforward in some parts. There were almost no information on using PF4J from Clojure, so I've wrote this post, explaining what I've did to make things work by creating example plugin, as per PF4J demo application. Hope it will be useful for someone!

Even since the microservices craze started, some cooler heads have prevailed. In particular, Oliver Drotbohm, a developer on the Spring framework, has been a long-time proponent of the moduliths alternative. The idea is to keep a monolith but design it around modules.

Not sure if that will be complete example but for coding I would go trough Spring dev members in Github: - Olivier Gierke : https://github.com/moduliths/moduliths (Modulith) - Rossen Stoyanchev : https://github.com/rstoyanchev - Dave Syer : https://github.com/dsyer

Conceptually, there a lot of similarities to Moduliths. Moduliths helps you to build modular Spring Boot applications which are preferred to be deployed as a single unit. Like archifacts Moduliths uses ArchUnit to enforce certain architectural constraints and - based on some rules - it's able to identify the application's building blocks.

Moduliths - a Spring Boot extension that allows to structure your application into logical modules, test those individually and derive high-level documentation for the structure created.