background preloader

Article

Facebook Twitter

Blog

Architecture. Service Composition. The majority of SOA publications are concentrating on definition and implementations of the individual business services. Building enterprise solution(s) typically requires combining multiple existing enterprise services. These composite services can be in turn recursively composed with other services into higher level solutions, and so on. Such recursive composition of business services is one of the most important features of SOA, allowing to rapidly build new solutions based on the existing business services. As the amount of individual business services (and their compositions) grows, the easier it becomes to implement new enterprise solutions. The main drivers for the creation of composite-services, as defined in Toward a pattern language for Service-Oriented Architecture and Integration, are: Usage simplicity.

Composition Design Composition design is concerned with designing a solution based on a set of existing services. Service interactions Composition topologies Conclusion 1. SOA anti-patterns. A lot of emphasis has been placed on implementing Service Oriented Software according to best practices and principles. But how about the worst practices? In this article, Steve Jones from CapGemini goes over some of the most egregious and thorny antipatterns based on his experiences in the industry and discussions with other SOA thought leaders.

The purpose of patterns is to define how systems should be built in repeatable ways; the purpose of anti-patterns is to help you see when that hasn't been done. Format Each anti-pattern presented in this article will follow the following format: Description - What it is? Effect - What you see? Antipattern: The Shiny Nickel Also know as the "Magpie" Description Used to incorporate the latest technology buzz within your SOA for the sake of telling people about it. Effect SOA projects are characterised by their use of new technologies and their product procurement cycle more than the actual solution being delivered. Cause Resolution Antipattern: IT2B. Building Enterprise Services with Drools Rule Engine. By Birali Hakizumwami 01/17/2007 Using a rule engine provides a framework that allows a way to externalize business logic in a common place.

This will in turn empower business users and subject matter experts of the business to easily change and manage the rules. Coding such rules directly into the application makes application maintenance difficult and expensive because the rules change so often. This article goes into detail on how to architect and build a service that uses Drools to provide business decisions. This service can be part of the overall enterprise SOA infrastructure. As such, it can either be a standalone service that is consumed in a one-to-many model by all contracted consumers, or part of a composite service that provides a complex business functionality. To illustrate this point, the article shows how a service using the Drools rule engine can hide the complexity of automating mortgage underwriting decisions that a mortgage company needs to make on a daily basis.

Java theory and practice: Urban performance legends, revisited.