 4/10 Good --- codebetter.com http://feeds.feedburner.com/SamGentile
| Connected Systems Lead East at Neudesic - Service-Oriented Architecture, Connected Systems, Enterprise Architecture, and Software Architecture from an experienced INETA Speaker and Solutions Architect MVP - Software Architecture, SOA, .NET Framework 3.5 WCF, Connected Systems, LINQ, VSTS, Windows Vista, Smart Clients, CLR, Rotor ... |
Friday, June 13, 2008 --- 119 days ago http://feeds.feedburner.com/~r/SamGentile/~3/303998981/soa-making-the-paradigm-s
 Last time in Part 3 , I talked about the definitions of SOA, from the Architectural and Business standpoints. Left over, was a discussion of the Four Tenets of SOA. However, we really do need to try to define a Service itself and see if there are any Design Patterns to help guide us in shaping what constitutes or becomes a service. These Design Patterns help to put the “A” in SOA and we will be spending a lot of time in Part 5 with the Architectural Patterns that make up SOA. First. let’s review from last time, the concept of Service Orientation (SO). Service Orientation is a general design concept or paradigm, a conceptual model for application-to-application and application-to-enterprise connectedness, composed of a specific set of design principles. The focus is on the data being transmitted, rather than a particular type system, operating system or platform. Applications that are built with a service oriented paradigm are concerned with sending or receiving messages that adhere to a specific structure. Applications that send and receive these messages are Services. Service Orientation has its own design paradigms and principles. design pattern catalogs, pattern languages, a distinct architectural model, and related concepts, technologies, and frameworks. [1] Service Oriented Principles, IMHO, are essentially a paradigm shift, a new skill set for developers to learn. Things that you emphasize in SO and SOA are often quite different ... |
|
|
Anytime
