What is a Mashup?
posted by Anna Mar, November 25, 2011Enterprises tend to over-engineer integration. Formal standards and complex tools such as JSR 286 Portal Servers, ESB and ETL are the common enterprise approach to integration.
On the internet things evolved differently. Internet companies had no time or patience for standards. They took the fastest route to integration with partners and customers: informal integration that generates parts of webpages.
Eventually, people gave a name to this approach to integration: Mashup. These are the characteristics of a Mashup:
HTTP, RPC, HTML, XML, JSON and/or JavaScript (usually)
contracts are defined by the publisher
services are located with a URL
integration is fast (time to market) and informal (no complex standards to follow)
integration is focused on displaying something on a webpage rather than inserting data in a database.
often the subscriber inserts a few lines of JavaScript into a HTML page to call the mashup
Enterprises are increasingly interested in Mashup integration and web oriented architecture in general.
Also check out our explanation of mashups in plain English.
|
Enterprise Architecture (EA) is supposed to help manage IT risks
— but is it possible that EA itself introduces new risks? |
|
Big data is on the rise — are you missing out? |
|
The exciting world of ITIL metrics. |
|
Service-oriented Architecture (SOA) is as simple as can be — it can all be boiled down to these 9 principles. |
Recently on Simplicable
| The 20 People In Your Organization Who Need Enterprise Architectureposted by Anna MarEnterprise architects are leaders. They're near the top of the technical food chain in any organization. As leaders, there are a lot of people in the organization EAs can help. |
| The 4 Contenders to be Your Next CIOposted by Anna MarWhen your organization looks internally for a new CIO there are four usual suspects. |
| Enterprise Software Guideposted by John SpaceyA guide to enterprise software that covers a wide variety of critical enterprise tools. |
|
