A path to modularity with Eclipse Virgo
Imagine the perfect world. Every piece of it is bright, shiny and meaningful. Every piece is at its place - that is harmony, isn’t it?
Now look at the real world. There are some bright pieces, for sure. It's not difficult to find them because they stand out in the sea of greyness and irrelevance to your own needs. You wish so much to be able to take exactly what you want and build your perfect world.
But you can't.
Because it's not easy to get these shiny blocks out of the grey. You should either take it all or leave it... Or?
When talking about modularity, people usually think of reusable blocks that could be put here and there, but always on top of something monolithic. The common understanding is that the foundation of every product should be monolithic. Because otherwise it's difficult (not to say impossible) to guarantee its quality, it is specific to the particular product and modularizing it wouldn't make sense. Really?
Join us to see Virgo on the modularity path! Your own flavor of Virgo could be built on the fly with only those features you really need. Let us introduce Virgo Nano - our smallest offering which brings the long-awaited p2 support and initial provisioning to Virgo. Don't need a server but you've heard of some cool internal Virgo features which you would love to have in your product?
Just name it:
- deadlock detection
- extensible and independent web console
- unsatisfied services detection
- load time weaving
- enhanced OSGi utilities
- sophisticated event logging and tracing
- extensible dump generation mechanism
Pick whatever you want! Some of the most popular Virgo features expand the horizons of modularity and will be provided separately for you to use in your own projects and runtimes.
If you enjoy building your future with your own hands, see you at this session.
Slides available at: