Let’s face it, on one level, service-oriented design is an effort to smooth over complexity. Wrapped in the service or at the other end of the service call is some rough hewn software artifact. Finding information about those artifacts is still like hunt-and-peck typing. So much for smooth sailing…
By submitting your personal information, you agree that TechTarget and its partners may contact you regarding relevant content, products and special offers.
We talked recently with Bill Wilkins, who together with others has founded Adjoovo to address these kind of metadata issues. Adjoovo contends project failure is often rooted in the fact that underlying metadata assets are ignored as an organization builds new services. The company is building out a more inclusive metadata repository, or framework. It sees limits that exist with some current SOA-style repositories.
Wilkins says that the mismanagement of what exists “leads to architectural fragmentation and much higher levels of complexity.” Wilkins comes to these considerations after experience with Sun Microsystems in its SOA, WOA and ESB efforts. Naturally, Java artifacts are among the artifacts Adjoovo will look to register.
“We are trying to provide a framework that can handle diverse artifacts,” he told SearchSOA.com.
The company recently fielded its first downloadable sample software in the form of an Adjoovo Spaces community edition, and is looking for interested users to try it out and provide feedback.