My question is pretty straightforward: What are the features of an application that force the developer to exploit OSGI-like system? What are the cases, when such a utility is unneeded?
I just posted the following link to another question (What does OSGi solve), but I think here it is an even better fit. Hal Hildebrand wrote a blog about why and when he thinks OSGi is helping your development/product.
The core essence of the (pretty long) post is that it helps especially when dealing with long running, complex enterprise projects. In particular in the long run, the benefit of having an enforced structure will pay out, but read for yourselves
EDIT: fixed broken link.
Use OSGI if you want some of:
- a very modular code structure (extreme case : each install has a different set of modules/plugins)
- to start/stop/upgrade a module without stopping the rest of the application
来源：https://stackoverflow.com/questions/1558720/when-should-i-use-a-platform-like-osgi-and-when-it-must-be-avoided