- Parallel Computing and Business Applications
- Dec 30, 2008
- Cory Isaacson explains how Software Pipelines architecture enables you to easily scale your application to any size, maximize your resources, and best of all, do all this and still maintain critical business transaction and integrity requirements.
|
- Project-Oriented SOA
- Apr 7, 2009
- This article introduces an effective technique for moving your SOA program forward through an incremental, project-based approach.
|
- REST-Inspired SOA Design Patterns
- Mar 10, 2009
- Raj Balasubramanian presents a series of REST-inspired SOA patterns has been developed as candidate patterns for inclusion in the master SOA design patterns catalog.
|
- So, What Is This WCF Anyway?
- Feb 22, 2008
- Steve Resnick, Richard Crane and Chris Bowen walk us through the basics of Windows Communication Foundation.
|
- SOA and Web 2.0: Putting It All Together
- Dec 28, 2007
- Create a plan for your company's journey toward innovation by building and following a set of guiding principles and goals, as outlined in this chapter.
|
- SOA Basics
- Dec 13, 2010
- This chapter from 100 SOA Questions answers the questions,
what is SOA, is SOA an architectural style, what are fundamental constructs (the DNA) of SOA, what is the difference between a Web Service and an SOA service and what makes a project an SOA implementation?
|
- SOA Design Patterns: Capability Composition Patterns
- Nov 4, 2008
- Capability composition patterns build upon the service identification and definition patterns to establish the concept of service composition. Thomas Erl discusses this pattern in this chapter.
|
- SOA Design Patterns: Service Governance Patterns
- Jan 14, 2009
- This chapter covers several SOA patterns that have emerged to help evolve a service without compromising its responsibilities as an active member of a service inventory.
|
- SOA Governance: Governing the Service Factory
- Feb 19, 2009
- This chapter covers a practical approach for governing both the operation of the service factory and the management of services after they have been deployed to production.
|
- SOA Pattern (#13): Canonical Protocol
- Apr 29, 2010
- The Canonical Protocol design pattern is one of the inventory standardization patterns that aims to elevate the composition-centric characteristic of SOA by making services interoperable with each other. By enforcing the use of a common communication framework, it eliminates the need for protocol bridging and increases the reusability and the recomposability potential of services in a service inventory.
|
- SOA Pattern (#1): Service Façade
- Jan 20, 2009
- Thomas Erl brings you the first SOA Pattern of the Week.
|
- SOA Pattern (#10): Service Refactoring
- Mar 9, 2010
- At some point during its lifetime a service might need to be enhanced or modified as a result of an external or an internal stimulus. The Service Refactoring design pattern addresses this issue in a manner so that the existing service consumers are not affected by the required change.
|
- SOA Pattern (#11): Event-Driven Messaging
- Mar 27, 2010
- The Event-Driven Messaging design pattern attempts to address the inefficiencies related to the use of the traditional polling based model by suggesting a publisher-subscriber based model whereby a service interaction occurs only when an event occurs within the boundary of the service provider.
|
- SOA Pattern (#12): Service Layers
- Apr 20, 2010
- The Service Layers design pattern attempts to standardize the way services are designed within a service inventory by organizing services into logical layers that share a common type of functionality. By structuring the service inventory around common types of functionalities, this design pattern eases the evolution of services and reduces their governance burden.
|
- SOA Pattern (#14): Logic Centralization
- Jun 11, 2010
- The Logic Centralization pattern is one of the basic inventory design patterns that structures the service inventory in a way so that it is free from redundant solution logic and endeavors to increase the reuse potential of agnostic services by enforcing use of agnostic services according to their functional boundaries.
|
- SOA Pattern (#2): Non-Agnostic Context
- Jan 28, 2009
- Should a service only be considered a service if itβs reusable?
|
- SOA Pattern (#3): Domain Inventory
- Feb 5, 2009
- You are not required to carry out an enterprise-wide adoption of SOA in order to realize its benefits. This is the very reason the Domain Inventory pattern emerged.
|
- SOA Pattern (#4): Service Normalization
- Feb 25, 2009
- Like data normalization, the Service Normalization pattern is intent on reducing redundancy and waste in order to avoid the governance burden associated with having to maintain and synchronize similar or duplicate bodies of service logic.
|
- SOA Pattern (#5): Service Decomposition
- Apr 2, 2009
- The Service Decomposition pattern provides a technique for splitting up a service after its initial deployment into two or more fine-grained services.
|
- SOA Pattern (#6): Canonical Schema
- May 19, 2009
- Of all the patterns in the SOA design patterns catalog there is perhaps no other as simple to understand yet as difficult to apply in practice as Canonical Schema.
|