Tracking change and innovation in the enterprise software development community
Terracotta:
Scale your
Apps w/ease
Offload the DB:
Learn More!
QCon San Francisco
Nov 19-21:
+ 80 sessions & tracks
Register now
and Save $400!
IBM WebSphere
Virtualize apps
to lower costs,
Increase agility
Learn more!
Create REST
-enabled Web Apps
with Project Zero
from IBM.
Posted by Scott Delap on Jan 18, 2008 08:42 AM
Bill Kayser of Nagarro recently detailed his experience moving an application to OSGi from a custom infrastructure and build process. In the first of two blog entries on the endeavor, he provides an interesting introduction to OSGi from the perspective of SOA in a JVM. In the second entry he covers the conversion process itself. The driving reasons for moving to OSGi were based on business requirements. However, Kayser was pleasantly surprised by the other benefits that were gained:...The improvements included but were not limited to:
...To this day team members still come up to me occasionally to thank me for introducing OSGi, often after being reminded what things were like by having to go back to an old release build...
- Going from 25,000 lines of ant code required for a full build down to about 200 lines of boilerplate configuration, plus about 200 lines of custom callbacks,
- We eliminated about seventy class file catalogs used to ensure extra classes were not inadvertently shipped in the wrong jar file or duplicated unnecessarily,
- Reducing the size of application distros by eliminating unused dependencies
- Surfacing previously unknown bugs based on dangling references to missing classes and libraries,
- Eliminating a large body of code devoted to managing extensions with segregated class spaces using custom class loaders.
- Going from managing four different runtime configurations for each application–the IDE classpaths, the IDE launchers, the runtime script classpaths, the build script classpaths–down to a single feature descriptor listing the OSGi bundles comprised by each application.
On a related topic Red Monk's Michael Coté recently published the OSGi in Java - Eclipse Equinox Screencast and Video Series, sponsored by the Eclipse Foundation. Coté tackles topics such as an introduction to Enterprise OSGi, Ajax with Eclipse RAP, and OSGi on the Server-Side.
Hibernate without Database Bottlenecks
RESTful todo list sample tutorial with Groovy & Project Zero
Scale your applications without punishing your database
Introducing application infrastructure virtualization and WebSphere Virtual Enterprise
IBM software architect eKit: Grady Booch podcast, whitepapers, articles
Thin client paradigm characterized by web applications is a kludge that needs to be repudiated. Old compromises are no longer needed and it's time to move the presentation tier to where it belongs.
In this presentation filmed during QCon 2007, Jeff Sutherland, the creator of Scrum, talks about his visit at Google to do an analysis of Google's first implementation of Scrum.
In this article, Bryon Jacob and Chris Berry introduce AtomServer, their implementation of a full-fledged Atom Store based on Apache Abdera, which is now available as open source.
It is easy to think that virtualization applies only to servers. In reality the recent resurgence of the concept is also being applied to networking, storage, and application infrastructure.
In this article, Stefan Tilkov explains some of the most common anti-patterns found in applications that claim to follow a "RESTful" design and suggests ways to avoid them.
In this article, Adrien Louis and Marc Dutoo discuss the differences and relative merits of using orchestration vs. routing in a typical ESB setup, and discuss various implementation options.
Wayne Lund discusses batch processing, Spring Batch objectives and features, scenarios for usage, Spring Batch architecture, scaling, example code, failures and retrying, and the future roadmap.
Developer Jay Fields draws on his experiences as a ThoughtWorks consultant to describe effective user story estimation techniques.
No comments
Reply