InfoQ Homepage SOA Content on InfoQ
-
Presentation: Steve Vinoski on REST
In a presentation recorded at QCon San Francisco, CORBA guru Steve Vinoski introduces REST from the perspective of a traditional SOA person. He explains the goals of the various constraints REST imposes, and the desirable properties one can gain from adhering to them. In a hypothetical discussion with a "SOA guy", Steve addresses various frequent doubts people express when they first look at REST.
-
The Industrialisation of IT?
WS-CDL has struggled from birth to find mainstream acceptance. Now one of the main authors, Steve Ross-Talbot, has compared one of the principles behind WS-CDL, that of precision in defining services, to that of the micrometer during the early industrial revolution. Can WS-CDL have the same impact as the micrometer and really facilitate service reuse?
-
Did you Perform a Silo Analysis as part of your SOA Implementation?
Jeff Schneider provides a set of practical questions to guide governance activities through "Silo Analysis". He and others provide specific tips to avoid creating Silo Services, a common SOA anti-pattern.
-
The BPMN 2.0 Debate Continues
With the continuous merging between SOA and BPM, an attention to BPM design and implementation continues to attract the attention of bloggers whose comments span a wide range of problems from business process design to implementation.
-
Article: Rationalizing the presentation tier
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 article, Ganesh Prasad and Peter Svensson explains how and why.
-
Article: Beyond SOA, a New Type of Framework for Dynamic Business Applications - Part II
In the second part of their article, Vasile and Michael explore the architecture of Dynamic Business Application as a possible standard architecture for server-side applications. The authors note that in this architecture concepts like SOA play a minor role while components like BPM engines, schedulers, messaging have a definite role.
-
Introducing InfoSphere Mashup Hub from IBM
A mashup is a web application that combines data/functionality from more than one source into a single integrated application. Mashup’s popularity stems from the emphasis on interactive user participation. IBM InfoSphere MashupHub is a new lightweight information management environment for IT and business professionals who wish to use and/or share information for use in mashups.
-
The Open Group Releases Draft of SOA Ontology Standard
The SOA Working Group contributed to the Open Group a draft version of SOA Ontology 2.0. The standard defines a formal ontology for Service Oriented Architecture. The ontology is written in the Web Ontology Language (OWL) and contains classes and properties corresponding to the important concepts of SOA.
-
UDDI and the Framework for Web Services Implementation Technical Committees close
OASIS announces that the UDDI and FWSI technical committees have closed and completed their work.
-
Article: REST Anti-Patterns
In this InfoQ exclusive article, Stefan Tilkov discusses some of the oft-used anti-patterns for REST based development.
-
Agile Cloud Computing?
Almost a year on from their initial announcements around grids and cloud computing, Arjuna Technologies have released more details of what they're working on: a new Cloud-platform called Arjuna Agility that emphasises a non-invasive approach to getting the most out of your IT investments as they migrate to the cloud.
-
Is Enterprise Data Management the Third Face of the SOA/BPM Coin?
Fred Cummins, an EDS fellow, and SOA veteran, wrote an essay last week on "Data Management for SOA". He is looking at how some of the key tenets of service design ("loose coupling" and "autonomy") relate to enterprise data in the context of achieving reuse and enabling change.
-
Opinion: When Designing Your SOA - Taste is Everything
Dan Creswell claims that "taste is everything" when it comes to putting together the pieces that make a good SOA. Dan says that picking the technology stack for distributed services, how you layer the service "units", etc, are a matter of taste as well as consideration of a number of guidelines, as opposed to just taking a cookie cutter approach to SOA as some seem to claim is possible.
-
Interview: Mark Little on Transactions, Web Services, and REST
In this interview, recorded at QCon London 2008, Red Hat Director of Standards and Technical Development Manager for the SOA platform Mark Little talks about extended transaction models, the history of transaction standardization, their role for web services and loosely coupled systems, and the possibility of an end to the Web services vs. REST debate.
-
Einstein: an Experimental 4GL for SOA
SOA implementation typically requires usage of multiple technologies for implementing different SOA aspects. Such implementation is a daunting task, requiring, at a minimum, understanding different technologies, involved in typical SOA implementation. One of the possible solutions to this complexity is developing Domain Specific programming languages for SOA.