OSGi Community Event 2016 Presentation by Raymond Auge (Liferay, Inc.) Creating a modular system leads to a number of benefits, from technical improvements to organizational improvements. However, at scale modularity can require a significant amount of mental energy. The OSGi model is fundamentally based on the idea of injecting knowledge into individual modules which frameworks use to great effect. But given hundreds or thousands of modules the sheer volumn of information can make reasoning about them difficult. Luckily OSGi defines mechanisms for performing operations to reason over arbitrary number of modules. This talk will review and demonstrate the capabilities of these mechanism.

1. From JARs to Bundles to
Resolutions to Knowledge
Raymond Augé <raymond.auge@liferay.com>

2. Modularity!

3. Resolving Dependencies

4. The Artifact Identity Model

5. The Artifact Identity Repository
Model

6. Limitations of the Identity
Model

7. Ask yourself what your CTO
wants?

8. As a developer what do I want?

9. Evolve from Identity to
Requirements!

10. OSGi

11. The Requirements and
Capabilities Model

12. Standardized Expressions
See resources ->

13. Enriching Knowledge of
Artifacts

14. Mechanisms for Enrichment
See Resources ->

15. Resources at ->
https://github.com/rotty3000/osgi.web.boot.http.example/tree/osgice-2016-1
https://github.com/rotty3000/papersntalks/tree/osgice-2016-1/2016/OSGI-CE