beyond mashups: service integration and more

Beyond Mashups

this talk is basically a talk i give about web hooks, but in the context of mashups.the idea is you’re all familiar with mashup opportunity, made possible by APIs...web hooks are like the other side of APIs that will open up a new kind of opportunity

Mashup

this is my crude example of mashups. a datasource or two, perhaps a presentation tool,some magic glue... and sometimes packaged up as a widget or embeddedable something.housing maps as an example. it’s mostly about read-only or query based functionality.

Mashup

Datasource

this is my crude example of mashups. a datasource or two, perhaps a presentation tool,some magic glue... and sometimes packaged up as a widget or embeddedable something.housing maps as an example. it’s mostly about read-only or query based functionality.

Mashup

Datasource

Presentation

this is my crude example of mashups. a datasource or two, perhaps a presentation tool,some magic glue... and sometimes packaged up as a widget or embeddedable something.housing maps as an example. it’s mostly about read-only or query based functionality.

Mashup

Datasource

Presentation

Magic

this is my crude example of mashups. a datasource or two, perhaps a presentation tool,some magic glue... and sometimes packaged up as a widget or embeddedable something.housing maps as an example. it’s mostly about read-only or query based functionality.

Mashup

Datasource

Presentation

Magic

Widget

this is my crude example of mashups. a datasource or two, perhaps a presentation tool,some magic glue... and sometimes packaged up as a widget or embeddedable something.housing maps as an example. it’s mostly about read-only or query based functionality.

Mashup

Datasource

Presentation

Magic

Widget

this is my crude example of mashups. a datasource or two, perhaps a presentation tool,some magic glue... and sometimes packaged up as a widget or embeddedable something.housing maps as an example. it’s mostly about read-only or query based functionality.

Mashup

Datasource

Presentation

Magic

Widget

this is my crude example of mashups. a datasource or two, perhaps a presentation tool,some magic glue... and sometimes packaged up as a widget or embeddedable something.housing maps as an example. it’s mostly about read-only or query based functionality.

Mashup

Datasource

Presentation

Magic

Widget

this is my crude example of mashups. a datasource or two, perhaps a presentation tool,some magic glue... and sometimes packaged up as a widget or embeddedable something.housing maps as an example. it’s mostly about read-only or query based functionality.

Mashup

Datasource

Presentation

Magic

Widget

this is my crude example of mashups. a datasource or two, perhaps a presentation tool,some magic glue... and sometimes packaged up as a widget or embeddedable something.housing maps as an example. it’s mostly about read-only or query based functionality.

Mashup

Datasource

Presentation

Magic

Widget?

this is my crude example of mashups. a datasource or two, perhaps a presentation tool,some magic glue... and sometimes packaged up as a widget or embeddedable something.housing maps as an example. it’s mostly about read-only or query based functionality.

Web Service A Web Service B

Mashup

but this model is interesting in that it’s like combining web services to make something new

Web Service A Web Service B

Web Service C

which is really yet another, now third web service.

Web Service A Web Service B

Web Service C

Aggregation

this is aggregation. and while it’s obviously valuable, there’s another idea waitingto be appreciated...

Web Service A Web Service B

Integration

integration. just make my existing services *work together how i want*

Web Service A Web Service B

Integration

Make my existing tools work togetherto become more than the sum of the parts.

integration. just make my existing services *work together how i want*

The Programmable Web is a misnomer.

i believe in the programmable web. i want it, we have a glimpse of it. but we don’t have it. not really.

It should be called the Programmatic Web.

instead, API’s give us *programmatic* access to their services. we cannot “program” them, change them or customize them,or truly *compose* them like we’ve envisioned with the pipes metaphor

WEB HOOKSProgrammable World of Tomorrow

and the

Jeff Lindsayenter web hooks. please see other slides...