Print

From the Editors: OSGi is too complex



Email
April 15, 2010 —  (Page 1 of 2)
Any Java developer, especially one who works with open-source software, will tell you that being the build monkey is a thankless job. You spend all of your time digging through Ant XML files and pulling down the proper classes and methods from constantly updated libraries and packages around the Internet and your internal repositories. Isn't there anything that can save Java from the endless complexity of dependencies?

Well, there's the OSGi development model, which was hailed as the enterprise developer’s way to make a modular Java server application without the never-ending burden of dependency wrangling. OSGi promises sane dependency injections with tightly integrated modular code—and the ability to hot-swap code in and out of a running application server without the need for a restart. It's everything Java developers have asked for, right?

Well, yes and no. Yes, in that OSGi is supported by the Java industry, and in that software companies have begun building OSGi support into their servers and development tools. No, in that few enterprise developers seem to be adopting OSGi.

Why is that? We believe that OSGi, rather than simplifying server application development, has actually made it more complex, and there aren’t sufficient benefits to justify the added complexity.

The industry seems to understand the problem. SpringSource donated its DM Server to the Eclipse Foundation earlier this year to spur enterprise uptake of OSGi, and even Eclipse Foundation director Mike Milinkovich admits there's a lot of work left to be done to expand enterprise uptake of the OSGi development model.

We’re not convinced that OSGi is worth the effort, and there’s no doubt that there’s a long road ahead. Milinkovich and Maven creator Jason van Zyl both estimated it would take OSGi another two years before the tooling and development model are friendly enough to spur uptake in the enterprise.

And what’s the benefit again? Enterprise developers have written many, many server-side Java applications without using OSGi. We believe that, unless something significantly changes, OSGi isn’t worth the enterprise investment.



Related Search Term(s): open source, OSGi

Pages 1 2 


Share this link: http://sdt.bz/34281
 
Most Read  Latest News  Resources


Comments


04/15/2010 11:16:50 AM EST

You are of course entitled to your opinions, but unless statements such as "we believe that OSGi ... has actually made [app development] more complex" are backed up with data, that's all this piece has to offer: opinion. And in fact it is simply and demonstrably wrong. I'm unconvinced that NOT using OSGi is worth the effort.

United KingdomNeil Bartlett


04/15/2010 01:41:16 PM EST

The reason for the change towards OSGi is that IT shops need to be more agile in their software infrastructures. The current Java infrastructure is too heavy weight and OSGi enables a more streamlined approach. Right now the use of OSGi has been in building the Java servers, not exposing OSGi to the enterprise customers. That is coming now, so I think you will need to reassess in 12-18 months. Ian Skerrett Eclipse Foundation

CanadaIan Skerrett


04/15/2010 06:34:36 PM EST

Everything is difficult until it becomes easy. What you mean is that OSGi is hard to get your head around. However, this is not the same as beeing complex. After the OSGi concepts have been digested, it will make systems less complex. Modules and service architecture are the next step in SD. OSGi is offering both. Don't be afraid, it won't bite you.

NetherlandsWim Jongman


04/21/2010 11:12:27 AM EST

OSGi is by far the easiest way to build modular and extensible system. We are not building the same software as we did 5 years ago. Users expect consistent and agile information system : New functionality needs to be pluggable to the existing ones. To my point of view, It's all about time to market issues. Of course if you don't try to modularize your software, OSGi will be (mostly) worthless... But who don't today ???

FrancePascal Leclercq


04/22/2010 03:08:53 AM EST

I don't get the article at all. Is it about to implement the OSGi platform or just to build applications against it. I don't know anything about the first one, but the second one is not complex, at least not because of OSGi, but more because of the problem to break up your application into independent components. And by the way what have the different licensing models to do with OSGi?

AustriaKurt Graller


04/22/2010 11:20:59 AM EST

You many not think OSGi is worth the effort - but I know a number of CxO's in large organisations that disagree. OSGi is NOT a short term trend / fashion / (we have too many of those in the software industry!) - but a force that fundamentally re-shape the software. It may be 2 years away before it hits "main stream" - but the early adopters are moving. Some of the largest organisations have started putting OSGi migration plans into action. Meanwhile if you "believe" OSGi is difficult, please have a look at Nimble (https://store.paremus.com/nimble_download_with_30_day_license/ ) and see just how simple and elegant OSGi already is!

United KingdomRichard Nicholson


close
NEXT ARTICLE
SD Times Blog: Microsoft Open Tech turns one
Subsidiary advances Microsoft's cooperative stance toward open source Read More...
 
 
 




News on Monday  more>>
Android Developer News  more>>
SharePoint Tech Report  more>>
Big Data TechReport  more>>

   
 
 

 


Download Current Issue
MAY 2013 PDF ISSUE

Need Back Issues?
DOWNLOAD HERE

Want to subscribe?