The abstact is here:
Forrester Research predicts that mashups will be a $682 million industry in the next 5 years. But can you define mashups? Can you describe the value of mashups to an SOA architect or even a business user? Can you outline the relationship between mashups and existing enterprise technology? Knowing the answers to these questions will advance you well down the road to embracing the concepts and techniques behind mashups in your organization.
This three-part series will help you get a head start by discussing the gritty details. In Part 1 we'll define a mashup in the context of the enterprise, contrast it against other common data integration technologies, and outline some of the more important architectural elements. In Part 2 we'll discuss why SOA architects should care about enterprise mashups. Finally, in Part 3 we'll discuss an enterprise architecture that incorporates mashups as part of your SOA-enabled ERP/CRM/SFA/BI and homegrown applications.
A PDF version is here.
Labels: Service Component Architecture, Service Data Objects
0 Comments:
Post a Comment
<< Home