I am trying to find examples of implementations of Web 2.0 concepts/technologies in the enterprise in advance of my upcoming panel: “Web 2.0 and the Enterprise”. I was therefore very interested in David Berlind’s recent post on “Rethinking BPM in a mashup-based SOA world” – a worthy read if you are tracking the topic.
There are a large number of issues involving enterprise mashups, David pointing out to a couple of them:
To wit, attendees from the banking and government sectors have questions about the management of user IDs across domains (when a mashup involves multiple APIs each of which relies on its own identity management technology) as well as the reliability of public components. For example, if an enterprise dispatch application along the lines of what Kemsley describes above relies on Google or Yahoo for its mapping component, enterprise architects want to know what Google and Yahoo are doing to ensure the uptime of the relevant APIs (a particularly relevant question given the recent outages at the Software-as-a-Service-based Salesforce.com).
Best practices on the API evolution front are also a concern; not just to enterprise architects, but also to mashup developers looking to turn their innovation into a business. As API providers improve their APIs, what measures are they taking to make sure that those improvements don’t break the existing applications and mashups that rely on them (can you imagine an enterprise application grinding to a halt due to changes in one of the APIs it relies on?).