Mashups: The next major new application development model?

Discussions

News: Mashups: The next major new application development model?

  1. The Web continues to drive the evolution of innovation in software these days with REST challenging SOAP, RSS challenging notions of traditional content silos, and widgets putting a easily consumable, visual "face" on our service-oriented architectures. Our services and even our back-end functionality is getting increasingly atomized and made portable. In fact, the rise of widgets, gadgets, and badges on the Web is facilitating the low-barrier integration of very high value functionality into their Web apps in literally just a few minutes by almost anyone. This trend of ad hoc remixing services and content into new Web apps has been dubbed "mashups" and has generated over 2,000 major new Web apps alone in the last couple of years according to Programmable Web. Users are even doing this themselves en masse in their own blogs, wikis, and social networking profiles proving both the ease of use and dramatically driving the demand for Web parts that can be integrated with little more than a cut-and-paste. Are we witnessing a sea change in consumption of server-side services, integration models, and the rise of a new high speed, agile application development model? It appears so and the do-it-yourself era of software might be upon us as the Web turns into a sort of giant Home Depot of off-the-shelf parts and services. Not sure this is true? Check out the thousands of ready-to-use components available at WidgetBox, most of them connected to back-end Web services to provide functionality. Over at ZDNet, the new article "Mashups: The next major new application development model?" explores the challenges and major market opportunities in what might be a generational change in our apps.

    Threaded Messages (9)

  2. Mashup is an example of resource oriented computing. So is Yahoo! Pipes. We see the programmable web as being just the precursor to a fundamentally new approach to computing. The real impact from this shift will occur when we start to make Webable Programs. We have a whitepaper that describes the principles of resource oriented computing and introduces a general purpose ROC platform. http://1060research.com/netkernel/whitepapers/
  3. Mashup is an example of resource oriented computing. So is Yahoo! Pipes.

    We see the programmable web as being just the precursor to a fundamentally new approach to computing. The real impact from this shift will occur when we start to make Webable Programs.

    We have a whitepaper that describes the principles of resource oriented computing and introduces a general purpose ROC platform.

    http://1060research.com/netkernel/whitepapers/
    Is this just simply a way to describe RESTful apps? Also what are Webable programs? Ilya
  4. REST is a subset of ROC. But ROC isn't constrained to the Web. ROC takes web-like resource composition inside to the program itself. That's what the glib phrase "Webable Program" is trying to convey. The whitepaper explains in depth.
  5. I wonder what this means in the enterprise space, in particular for corporate acquisition and product integration scenario. Could a mashup/ajax based front end coupled with ESB mesaaging bus enabled integrated back end suite of products be a viable solution, to build products based on a foundation of existing products. Pranab
  6. Machups wha![ Go to top ]

    I do not share the excitement when hearing the word 'mashups' (of course my view does not matter :). All this marketing techno mumbo-jumbo is just that...marketing crap. Anyway for those who enjoy new techno terms ... enjoy... i am sure the next word is around the corner.
  7. Re: Machups wha![ Go to top ]

    I do not share the excitement when hearing the word 'mashups' (of course my view does not matter :).

    All this marketing techno mumbo-jumbo is just that...marketing crap. Anyway for those who enjoy new techno terms ... enjoy... i am sure the next word is around the corner.
    +1 Pundits seem to constantly ignore the hard problems while emphasizing how easy it is to solve the easy problems.
  8. Re: Machups wha![ Go to top ]

    All this marketing techno mumbo-jumbo is just that...marketing crap. Anyway for those who enjoy new techno terms ... enjoy... i am sure the next word is around the corner.
    Did you seriously look into this, before pronouncing it as marketing techno mumbo-jumbo. If you did, please share your thoughts.
  9. Re: Machups wha![ Go to top ]

    I do not share the excitement when hearing the word 'mashups' (of course my view does not matter :).

    All this marketing techno mumbo-jumbo is just that...marketing crap. Anyway for those who enjoy new techno terms ... enjoy... i am sure the next word is around the corner.
    A++. I wonder where the real world, real value mashed-up business case is. Unless the widgets can talk to their server, to their host and to each other in a standarized, secure, portable, billable way, unless they can assure performance and general quality of service, defined behaviour in case of failure, provide multi version support etc. I do not see any vendors "mashup" as a viable development paradigm. As an ironic sideline note that the characteristics outlined above are to my knowledge not even fulfilled by a single "SOA" product or a single "Portal" product. But, hey sure, mashups are going to solve all or problems┬┤.
  10. MOst people dont realize...[ Go to top ]

    Even trivial business applications are more complicated than Google maps which is where this mashup stuff started. I havent worked on a single business application that had rules as simple as google maps. But people are wowed with the pics. So be it. Wow. When a single multi-party transaction can be performed via a mashup let me know. Ill be dead by then and so will you.