Enterprise Mashups: why do I care?

  • 4,337 views
Uploaded on

Enterprise Mashups are important since they bridge a void between the web and the enterprise behind the firewall. They break down traditional barriers around data and open up powerful new ways for …

Enterprise Mashups are important since they bridge a void between the web and the enterprise behind the firewall. They break down traditional barriers around data and open up powerful new ways for enterprises to leverage the web as a platform. This session will introduce some mashup concepts, discuss a number of software patterns and describe ways in which enterprises could do more with their applications, and provide a good grounding and practical knowledge about the emerging trend of Enterprise Mashups and how they might apply to the enterprise.

As the barriers break down developers should have an understanding of the implications and how the pieces fit together. Attendees will learn what enterprise mashups are, what they are not, and get to know some mashup patterns.

More in: Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads

Views

Total Views
4,337
On Slideshare
0
From Embeds
0
Number of Embeds
27

Actions

Shares
Downloads
101
Comments
0
Likes
3

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide
  • WHAT: One of the first mashups House listings on Craigs list plotted on google maps. If there isn’t a map it ain’t a mashup! Definition: The term mashup is primarily used to describe a remix [1] of digital data . It implies easy, fast integration, frequently using open APIs and data sources to produce enriching results that were not the original reason for producing the raw source data. Combining data and services from different providers to create new application.
  • WHAT: Distribution of services used to create mashups on the web Most interesting is the number of APIs out there to build Mashups: Everything from Telephony and SMS, to News APIs to Video to Maps Progammable web stats: 4,682 mashups; 1,745 APIS
  • WHAT :NEEDS WORK
  • WHAT: Statistics on new mashups in the last 14 days Enterprise focus is growing (progarmmable web not really a good source since most enterprise mashaps will be behind the firewall) Salesforce is the Google Maps for enterprise mashups
  • WHY: mashups make sense Put another way 80% of problems are not addressed by IT The way we have been building software is expensive, as such we need to decide carefully which applications to build Many users don’t get what they need
  • WHY: Critics,
  • Define the relationship between SOA and Mashup - Mashups in SOA world are ‘Composite Applications’ - Built with enterprise tools such as ESB, BPM Enterprise Mashups mix enterprise and web and SaaS
  • The killer may well be the platform not the user application
  • Harvest : Mine one or more resources for unique data Enhance : Extended the capabilities of existing resources Assemble : Remix existing data and interfaces to serve new purposes Manage : Leverage the investment in existing assets more effectively Test : Verify the performance and reliability of applications
  • Dramatically simplified integration for Tomcat applications Simple API using annotations – no concepts or architecture Works in conjunction with other open source frameworks (e.g., JSP, JSF, Struts, Spring) Task-based integration, e.g.: Send/receive email Subscribe to JMS queue Poll RSS or Twitter feed Publish REST service Built with the cloud in mind Ideal for open source community model – “App Store for iBeans”

Transcript

  • 1. Enterprise Mashups why do I care? Ross Mason, MuleSoft
  • 2. About Me
  • 3. Agenda What? Why? How?
  • 4. Mashups
  • 5. Mashup Stats
  • 6. What is being mashed REST Services RSS/ATOM Feeds Web Pages Email XML Database JSON Mashups
  • 7. Enterprise Mashups
    • +
    +
  • 8. What is being mashed REST Services RSS/ATOM Feeds Web Pages Email XML Database JSON Enterprise Mashups Messaging (JMS, AMQP) File / FTP CSV, Text Enterprise Apps Binary (PDF, Excel)
  • 9. Web vs the Enterprise Web Mashups Enterprise Mashups Visual centric Data & Information centric Simple Data relationships Deep transformation & semantic relationships End-user driven Developer & business analyst driven Use Public APIs Combination of Public and internal services No QoS guarantees Enterprise QoS Simple Web Security Policy-based security
  • 10. Recent Mashup Stats
  • 11. The Looooong Tail
    • IT focuses on 20% of problems that affect 80% of their users
  • 12. You can’t build a business case for Enterprise Mashups … you can’t build a general business case for mashups, [but] you can build a specific mashup-centric business cases - Anthony Bradley Gartner
  • 13. Mashups: fail
    • Hard to define
    • Aimed at “users” not “developers”
    • No single value prop
    • Difficult to sell to the business
    • Tens of mashup platforms shut down
  • 14. Brighter Future
    • We don’t throw anything away
    • 88.23% of applications need to integrate with other applications
    • Wealth of public APIs is growing rapidly
    • Evolution of SOA in the enterprise
    • Wealth of rapid development frameworks
  • 15. Users vs Developers
    • Users don’t build software
    • Mashup platform, foreign concept
    • Mashup in context
    • Need data in consumption form
    • Microsoft Excel has the right balance
  • 16. Mashup timeline MS Excel mashups emerge Enterprise Portals and JSR-168 started Yahoo! & others introduce Web portals 1993 1998 2003 2000 AJAX is coined, Fuels Web 2.0 Mozilla introduce Javascript XMLHttpRequest Open Mashup Alliance founded 2009 Google Maps API launched Yahoo! Pipes launched 2007 2005 Mule, first open source ESB Salesforce.com IPO. Term SaaS coined 1999 2004 2006 2008 2001/2 Enterprise mashup platforms emerge Forrester: Enterprise 2.0; $4.6bn Industry By 2013 MySpace & Google team up: OpenSocial 1,782 APIs on prog..web.com web enterprise
  • 17. What about SOA?
    • Enterprise mashups, SOA’s killer App?
    SOA Web 2.0 Enterprise Services Web Services / APIs Enterprise Mashups SaaS
  • 18. Mashups and the Cloud
    • New lease of life for Mashups
    • Natural fit, common context
    • PaaS = Next Gen. Mashup platform
    • Developer-focus
  • 19. The Smart Revolution
    • Geo-location
    • Situational data
    • Telephony services
    • Barcode scanning
    • Image-recognition
    • Augmented reality
  • 20. Where is the killer app? The mashup's strength lies in discovering the atypical, in exploiting data in new ways. - Dion Hinchcliff
  • 21. Patterns
  • 22.  
  • 23. Patterns Harvest Enhance Assemble Manage Alerter Accessibility Content Aggregation Content Migration API Enabler Feed Factory Dist. Drill down Portal Enabler Competitive Analysis Field Medic Emergency Response Quick PoC Infinite Monkeys Folksonomy Enabler Content Integration Single Sign-on Leading Indicator Smart Suggestions Fliter Widget Enabler Reality Mining Super Search Location Mapping Reputation Mgmt Translation Splinter Time Series Workflow
  • 24. Feed Factory Feed Factory aggregated feed RSS Feed Relational Database Sales Activity Report Atom Feed feed data Feed Consumer
  • 25. Super Search Super Search aggregated data Content Management System Relational Database Data APIs Search Engine Search data Search Mashup File System
  • 26. Pipeline Data Source Mashup Transformer Web Service Call Transform Route
  • 27. iBeans easy mashups
  • 28. Foundation
    • Abstraction for the complexity of SOA
    • Open source framework
    • Lineage, pedigree of Mule ESB
    • 15+ iBeans ready for production
    “ Micro-light ESB”
  • 29. Communication
    • Reusable Java modules
    • Bean interface to networked services
      • Not just SOAP, REST
    • Communications channels
      • Ajax from JavaScript
      • RPC
      • Java
  • 30. Use cases
    • Situations where an ESB is too heavy
    • Social media app integrations
    • Easy cross-webapp reuse
    • Point-to-point integration
    • Seamless migration path to Mule ESB
  • 31. GPS Walker demo
  • 32. http://?.?.?.?:8080/gpswalker/cursor.html
  • 33. Overview
  • 34. The pieces Runtime Container: Tomcat, Tcat, (Mule) iBeans Runtime Channels: HTTP, SMTP, IMAP, REST, JDBC, JMS, XMPP, FTP Application Annotations Transform and Bindings Scheduler Web apps apps web your console iBean Objects Formats: JSON, RSS, ATOM, XML, SOAP
  • 35. Summary
    • Growing need to serve the long tail of applications
    • User-focus mashups unsuccessful
    • SOA and Web 2.0 keeps driving reuse
    • iBeans offers a developer-focused approached
  • 36.
    • Front (cogs): http://www.flickr.com/photos/balakov/309709612 Back: (questions) http://www.flickr.com/photos/doberagi/1404539812
    http://mulesoft.org/ibeans twitter: @rossmason http://blogs.mulesoft.org