1% of the members rule this place. Be one of them! Login and vote now.
By peterrietzler
via peterrietzler.blogspot.com
Published: Jan 11 2009 / 22:01
A few weeks ago I spotted an article that stated OSGi as "the next big thing after Spring". Actually, there are a whole bunch of articles, blogs etc... out there in the wild - all praising OSGi as one of the next "big things" that will reach many sectors in the Java space. I don't doubt this and I do admit that OSGi solves many problems and supports top notch architectural models such as high modularization and micro services. However, on the other side - after using OSGi for a couple of years and see how it performs (in the meaning of development performance) in different areas I really have doubts about OSGi.
Comments
cristian.malinescu replied ago:
Are we comparing apples vs oranges?! Look at the Spring + OSGi integration, that's the right angle. EJB's are components OSGi is a integration service container.
peterrietzler replied ago:
Did you read the article ? Nobody is comparing OSGi and EJB ...
,
cristian.malinescu replied ago:
Yes, and first I read the title. It is baffled from that point. Still I can't see how a service/integration oriented framework can evolve the same way as a component oriented container. The factors involved in evaluation of the OSGi future endeavors versus EJB are totally different, their purpose and paradigm is different.
OSGi adds to Java platform very powerful, long time requested features, like dynamic class loading etc. Eclipse isn't anymore else than an OSGi container hosting mainly UI producing services - and more; EJB is exclusive server side targeted, OSGi - everywhere. In term of complexity - OSGi is far more easier to handle than EJB. I do OSGi programing for the Eclipse platform for more than 1 year. It seems that Rod and Co. @ Spring decided that supporting OSGi ... isn't going to be a rocket science task?!
Voters For This Link (22)
Voters Against This Link (1)