Solved by Expert Tutors
Patterns are the abstraction of an idea in a reusable form. The most simple and most frequently used pattern in our daily life is the pattern in the...
Solved by Expert Tutors
Question

Patterns are the abstraction of an idea in a reusable form. The most

simple and most frequently used pattern in our daily life is the pattern in the language.
There are some intimate relationships between pattern and complexity. Using pattern to deal complexity is an intuitive strategy in military, business, and politics since ancient times. There are constantly changing contexts in each of these domains but many of them are similar thus could be resolved by the same strategy. The pattern, a combination of both the abstract form of the context and the solution thus became the best way to learn and to use.
This is especially true in Eastern civilizations, in which, complexity phenomenon was not analyzed by using deduction but treated as a whole and learned in pattern. A prime example was “The Art of War” by Sun Tzu (544~496 BC), it is a military treatise consists of 36 most commonly encountered military combats patterns and now being widely adapted into business and international relations environments.
In modern times, though deductive method was widely used in engineering field, pattern still provides a proven strategy to deal with problems in a discipline that cannot be described quantitatively. Design is such a discipline.
Introducing pattern into design engineering was probably started by Christopher Alexander, an Austrian-born American architect. In his now classic, “A Pattern Language: Towns, Buildings, Construction (1977),” he summarized about 250 different traditional architecture design patterns. The work by Alexander inspired a group of programmers and the idea of using pattern to describe software engineering solutions was introduced in 1987 by Kent Beck and Ward Cunningham as well as others during a meeting. In 1994, the first book about software design pattern, “Design Patterns: Elements of Reusable Object-Oriented Software” was published.
 
 
Messaging Patterns
Ten years later (2004), probably the first book about enterprise integration patterns (by Gregor Hohpe) was published. The idea of using pattern to summarize the nuts and bolts of enterprise integration solutions was admittedly a natural extension from software design pattern and architecture design pattern. Though the name is called enterprise integration, the pattern discussed here are messaging system, the middleware of enterprise integration. It is not a surprise because messaging is the glue to connect the information archipelago together. Arrived relatively late in enterprise computing, middleware emerged in 1980s as a solution to link new applications to old legacy systems.  This bottom-up approach for integration is the main approach for almost all major enterprises due to the existence and irreplaceable of legacy systems. This is also the situation we are currently experienced. So the patterns described here are derived from years of actual field experience when dealing with such integration projects.
The first three chapters of “Enterprise Integration Patterns” provide a good overview of patterns in enterprise integration. Here is the table of contents and let’s review Introduction, Chapter 1 (Integration Styles), Chapter 2 (Messaging Systems), and Chapter 3 (Messaging Systems) this week. All chapters are very well written. The Widgets and Gadget’s ‘R US example in chapter 1 will give you a good idea of how and why pattern should be used in integration. The one-minute EAI section before the example is also a good illustration of how tricky a simple integration could be. Chapter 2 introduces four macro-integration patterns though the later chapters were mainly focused on messaging, the last pattern in this chapter. Chapter 3 introduces the major pattern categories in a messaging system.  
SOA Patterns
The patterns summarized in Hohpe’s book were mainly about messaging systems, the middleware in enterprise integration that could link existing and new systems. SOA has impacts on system design and development in many levels. It not only involves technical interaction between components and/or Web services but also involve the organization of different services to meet standard business routines or service composition.
Reading [3] gives a good introduction of the new aspects of SOA patterns.  For SOA pattern details, please review book by Rotem-Gal-Oz (http://arnon.me/soa-patterns/ ) and chapter 1 and 10 are provided in reading list.
 
Readings:
[1] Gregor Hohpe, “Enterprise Integration Patterns”, related chapters, 2004
[2] Arnon Rotem-Gal-Oz book “SOA Patterns”, Chapter 1 and Chapter 10, 2012
[3] Gregor Hohpe, “SOA Patterns – New Insights or Recycled Knowledge?”
On basis of above information provided please write a report. Is the software as a service in Cloud computing similar to Web Service? What are their similarities and differences? What is the impact of cloud computing on SOA and enterprise integration? Please analyze this from platform, infrastructure, application, and user aspects, etc. 
a minimum of 3 pages (double spaced, 12 font size) are expected for report. report should also come with proper title and references. No plagiarism. 

Step-by-step answer

ng elit. Nam lacinia pulvinar tortor nec facilisis. Pellentesque

a. Fusce dui lectus, congue vel laoreet ac, dictum vitae odio. Donec aliquet. Lorem ipsum dolor sit amet, consectetur adipiscing elit. Nam lacinia pulvinar tortor nec facilisis. Pellentesque dapibus

ce dui lectus, congue vel laoreet ac, dictum vitae odio. Don

, dictum vitae odio. Donec aliquet. Lorem ipsum dolor sit amet, consectetur adipiscing elit. Nam lacinia pulvinar tortor nec facilisis. Pellentesque dapibus efficitur laoreet. Nam risus ante, dapibus a molestie consequat, ultrices ac magna. Fusce dui lectus, congue vel laoreet ac, dictum vitae odio. Donec aliquet. Lorem ipsum dolor sit amet,

m ipsum dolor sit amet, consectetur adipiscing elit. Nam lacinia pulvinar tortor nec facilisis. Pellentesque

acinia pulvinar tortor nec facilisis. Pellentesque dapibus efficitur laoreet. Nam risus ante, dapibus a molestie consequat, ultrices ac magna. Fusce dui lectus, congue vel laoreet ac, dictum vitae odio. Donec aliquet. Lorem ipsum

facilisis. Pellentesque dapibus efficitur laoreet. Nam risus

icitur laoreet. Nam risus ante, dapibus a molestie consequat, ultrices ac magna. Fusce dui lectus, congue vel laoreet ac, dictum vitae odio. Donec aliquet. Lorem ip

a. Fusce dui lectus, congue vel laoreet ac, dictum vit

molestie consequat, ultrices ac magna. Fusce dui lectus, congue vel laoreet ac, dictu

or nec facilisis. Pellentesque

ipsum dolor sit amet, consectetur adipiscing elit. Nam lacinia pulvinar tortor nec facilisis. Pellent

dictum vitae odio. Donec aliquet. Lorem ipsum dolor sit amet, consectetur adipiscing elit. Nam lacinia pulvinar tor

facilisis. Pellentesque dapibus efficitur laoreet. Nam risus ante, dapibus a molestie consequat, ultrices ac magna. Fusce dui lectus,

or nec facilisis. Pellentesque dap

entesque dapibus efficitur laoreet. Nam risus ante, dapibus a molestie consequat, ultrices ac magna. Fusce dui lectus, congue vel laoreet ac, dictum vitae odio. Donec aliquet. Lorem ipsum dolor sit amet, consectetur adipiscing elit. Nam lac

dictum vitae odio. Donec aliquet. Lorem ipsum dolor sit amet, consectetu

rem ipsum dolor sit amet, consecte

nec facilisis. Pellentesque dapibus efficitur laoreet. Nam risus ante,

entesque dapibus efficitur laoreet. Nam risus ante, dapibus a molestie

fficitur laoreet. Nam risus ante, dapibus a molestie cons

Fusce dui lectus, congue vel laoreet ac, dictum vitae odio. Donec alique

or nec facilisis. Pellentesque dapibus efficitur laoreet. N

m risus ante, dapibus a molestie consequat, ultrices ac magna. Fusce dui lectus, congue vel laoreet ac, dictum vitae odio. Donec aliquet.

cing elit. Nam lacinia pulvinar tortor nec facilisis. Pellentesque dapibus efficitur laoreet. Nam risus ante, dapibus a molestie consequat,

rem ipsum dolor sit amet, consectetur adipiscing elit. Nam lacinia pulvinar tortor nec facilisis. Pellentesque dapibus efficitu

Subscribe to view the full answer

Why Join Course Hero?

Course Hero has all the homework and study help you need to succeed! We’ve got course-specific notes, study guides, and practice tests along with expert tutors.

  • -

    Study Documents

    Find the best study resources around, tagged to your specific courses. Share your own to gain free Course Hero access.

    Browse Documents
  • -

    Question & Answers

    Get one-on-one homework help from our expert tutors—available online 24/7. Ask your own questions or browse existing Q&A threads. Satisfaction guaranteed!

    Ask a Question
Let our 24/7 Computer Science tutors help you get unstuck! Ask your first question.
A+ icon
Ask Expert Tutors You can ask You can ask You can ask (will expire )
Answers in as fast as 15 minutes