Paul Mooney attempts to clear up some of the misunderstandings surrounding SOA considering the fact that many implementations are labeled as “SOA” but are not. He does that by describing an SOA journey from establishing a route (characteristics, goals, benefits), planning it (service inventory), making it (service design) and arriving at the destination (measuring success, governance).
Mike Amundsen asks, in an post that examines alternatives to how one might develop RESTful services in environments constrained to a choice of using just GET and POST.
In addition to well established principles and anti-principles, Steve Jones’ new post introduces the notion of non-principles of an SOA implementation and explains why they are important.
In his new post, Jason Bloomberg introduces two types of services – Entities and Tasks, and explains the role each type of services plays in building SOA systems.
Using Service Oriented Architecture (SOA) it is possible to lower the costs of information systems. Paradigms which are appropriate to database era are still being applied to SOA, resulting in counterproductive, and sometimes even dangerous designs. The author explores ways to achieve the potential of SOA initiatives by adhering to ten basic commandments.
“SOA Principles of Service Design” by Thomas Erl is an encyclopedia of service design principles needed to build SOA solutions. This article contains three supporting practices taken from the book: Service Profiles, Vocabularies, and Organizational Roles.
Cesare Pautasso presents a pattern-based design methodology used to build RESTful services, which is accompanied by an example used to draw a number of patterns: Uniform Contract, Entity Endpoint, Content Negotiation, Endpoint Redirection, Idempotent Capability. Pautasso also mentions a couple of anti-patterns: tunneling everything through HTTP/GET and HTTP/POST.
Communication is everywhere. The Windows Communication Foundation (WCF) can be used to design and develop service-oriented distributed solutions. This presentation shows the basics of WCF and how to solve common problems in distributed systems. Christian Weyer provides a practical approach to realizing distributed solutions with WCF - beyond the hype and 'Hello World'.
In this interview from QCon San Francisco 2008, Ian Robinson discusses REST vs. WS-*, REST contracts, WADL, how to approach company-wide SOA initiatives, how an SOA changes a company, SOA and Agile, tool support for REST, reuse and foreseeing client needs, versioning and the future of REST-based services in enterprise SOA development.
Composite Software offers a new level of granularity when compared to SaaS (Software as a Service). Composite Software is about enabling "right-sourcing", i.e. move (or keep) arbitrary small or large elements of functionality wherever it is the most cost effective to operate them, not just entire systems. Economically, "right-sourcing" is far more efficient than "outsourcing" and SaaS. The goal of this book is start by understanding today’s software construction processes and technologies and explore why and how it should be evolved to support core composition mechanisms.
