Structuring Applications With Or Without OSGi

An airhacks.fm conversation with Jürgen Albert (@JrgenAlbert6)
about: Checkout last episode with Jürgen Albert: "#175 Pragmatic
Modularity and OSGi", Why do we need a module?, related episodes:
"#151 Modularization, Monoliths, Micro Services, Clouds, Functions
and Kubernetes", "#160 Modules Are Needed, But Not Easy", Physical
vs. Logical modules. How to pick a perfect module, picocli for
building Java CLI applications, module as to to divide and conquer,
how to cut the modules, in OSGi the smallest module is the package,
OSGi core specification already understands modules, build time vs.
runtime dependency and manifest assembly, JAX-RS and Vaadin OSGi
"whiteboard", Peter Kriens started with the OSGi idea, the OSGi
phone, OSGi services and service registry, service registry
listener, OSGi Declarative Services provide lifecycle, OSGi vs.
kubernetes, Kubernetes solved the port collision problem, OSGi
remote services, the Eclipse OSGi project,

Jürgen Albert on twitter: @JrgenAlbert6, Jürgen's company: Data
In Motion