10 tips on how to prevent business value risk
One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
Posted by Jean-Jacques Dubray on Jan 02, 2008
Sun Microsystems started a tour in the US to present a comprehensive view of the technologies and approaches it recommends to build Service-Oriented-Architecture with Java Technology. In Seattle, the presenter was Thomas Barrett, SOA Technical Specialist at Sun.
Sun's target architecture is a composite application platform which is using reusable services either provided by third parties or built from legacy systems. Sun introduces SOA as a:
Track-tested architectural style for building applications using services available in a network (“The Network is the Computer”)
The presentation explains that SOA is best implemented with an ESB that provides resource and channel adapters as well as a series of build-in capabilities such as transformation, security, logging, routing...
Sun introduces the four layers of a Service Oriented Architecture:
Sun sees Web Services and REST as equally important for implementing Service Oriented Architectures. It is investing significantly in REST with:
Sun also presents BPEL as a critical technology for SOA. The presenter demoed a graphical editor based on BPMN symbols and running in NetBeans 6.0.
The presentation went on to give an introduction to JBI, which is Sun's foundation to Service Oriented Achitectures. The presenter also demoed JBI's new assembly capability which is very similar to the one of SCA. Sun sees JBI as:
The presentation gives some details about the upcoming JBI 2.0 specification:
The presentation includes a proposal for the alignment between SCA and JBI:
The last section of the presentation focuses on the OpenESB offering, its relationship to Java CAPS (Composite Application Platform Suite) and its roadmap.
JJ,
How is Sun combining their REST and BPEL stories? Obviously, with their emphasis on REST, they aren't supporting WSDL...
Jeff
Jeff:
hi, this is a good question. First I want to emphasize that the presenter, Thomas Barrett was neutral with respect to Web Services vs REST. I know that he relayed some of the concerns Tim Bray has about Web Services, but I did not get the feeling that Sun was walking away from Web Services. Thomas presented Tim's quote as: "what people that use REST think about Web Services". I am not sure he used the quote to represent Sun's view in the REST vs Web Services debate. I think Thomas point was "if you are thinking about Web Services, take a look at REST too".
BPEL appears to be a key element of CAPS (based on the presentation) and Thomas did not talk at all about the relationship between BPEL and REST.
IMHO, (it would be best if someone from Sun would respond directly) it seems that REST plays at the "access" layer of Sun's architecture. Of course, REST has more architectural implications than this, but nothing really prevents you to use REST as some kind of "lipstick". As soon as you use annotations on an object model, I think it means that you are doing some form of remoting without profound architectural changes. Again, this is only my opinion, and I am not conveying by expressing it anything I learned from Sun.
Hope this helps,
JJ-
One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.
InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.
Alex Papadimoulis discusses ugly code, where it comes from, how to avoid it, and how to get rid of it.
John Davies examines Visa’s architecture and shows how enterprises have architected complex integrations incorporating Hadoop, memcached, Ruby on Rails, and others to deliver innovative solutions.
Sean Comerford unveils ESPN.com’s architecture, what components are used and why, and the current changes the website goes through.
Are there repeated patterns of failure on Enterprise Agile Enablement efforts? Sanjiv and Arlen discuss Seven Deadly Sins to avoid when adopting Agile in an enterprise.
Erik Dörnenburg answers: What is Enterprise and Evolutionary Architecture?, discussing 4 issues: Turning strategy into execution, Ensuring conformance, Where do the architects sit? Buying or building?
Sean Cribbs explains what Map-Reduce and Riak are, why and how to use Map-Reduce with Riak, and how to convert SQL queries into their Map-Reduce equivalents.
2 comments
Watch Thread Reply