MashDowns - How to Improve Desktop and Enterprise Software by Mashing Up
From MashupCamp
This discussion will focus on using available software APIs and web services to improve existing desktop and enterprise software.
Discuss this topic online
The first generation of MashUps were largely super-cool, rapidly deployed ways of combining two or more web-based informational services to produce a new, more specifically useful information service. Take a bunch of stuff from the web, connect it, and make something new.
The next generation of MashUps, maybe called MashDowns, can be super-cool, rapidly deployed ways of combining existing or new desktop/enterprise software with web services and software modules to produce more robust applications. Take some useful desktop software, connect it with some stuff from the web, and make something that works better/faster/cheaper.
Potential sub-topics:
- what are existing examples of MashDowns (shameless self-promotion: ElephantDrive)?
- what are ideal opportunities for new MashDowns (are there existing software services that can be displaced by clever combinations of desktop software and web services)?
- does/can MashingDown produce a competitive advantage between software businesses (quicker deployment, more focus on core compentencies)? are there disadvantages inherent in MashingDown (lower barriers to entry, less control over IP)?
Session Notes (Day 1, 10 to 11 am, Room 8)
Attendees: TomOrtega Cindy H. Lu SandyKemsley
Tom's Notes (Official NoteTaker) MashDown
1st gen mashups (What?): Cool for users (consumers) Consumer super quick showing wow factor "neat" just because static/no process join data rapid, loose, public
2nd gen mashups (How?): Cool for business (enterprise) doing/application tying to desktop enterprise dependability redundancy because there's a need process/state combine service/state/process consumer grade, industrial strength, private
Problems w/ Adoption: Pride of Authorship Fear of loss of control "Not Invented Here" Authorization/Audit Trail Reliability Availability Financial aspects
Random Notes: Adhoc is inherent to mashups Business model idea Mashup as a development paradigM low total cost of ownership context dumb vs context aware why rebuild a service when someone else does it better and cheaper
Cindy's Notes:
1st Gen Mashups
- What?
- Cool for users
- Join data
- rapid, loose, public
- context dumb
2nd Gen Mashups
- How?
- Coll for businesses
- combine services/state/process
- Consumer grade, industrial strength, private, secure
- Context aware
Concerns for the enterprise mashups/environmental constraints
- Provisioning
- Reliability
- Serviceability
- Availability
- Performance
- Security
- Manageability
- Usability
Scott's notes/observations Mash Down – Mashing for competitive advantage in rich client enterprise apps
the notion of mashdown is conceptually akin to the salesforce.com “no software” slogan that integrates client apps within the business process using a single browser. they are not a mashdown, but that might provide the conceptual framework to start the discussion.
• 1st gen mashup focused on user (not context aware in terms of n/w state, connectivity, resource utilization, etc
• 2nd gen will focus on businesses – change the operating paradigm by supporting a business need (reduced cost structure, lowering capital requirements, providing a temporary service or expansion of capability and so on)
o will depend on how you can change the business model or business process through service or temporary service using mashdowns to achieve one of the above goals/objectives related to functionality resource management, etc. o e.g. use existing services to burst/surge abilities – enterprise resource mgt; data transformation/migration without confinement to proprietary systems
• there remains the longstanding IT organization’s need to get over the cultural mindset issues of NIH regarding what it thinks are its operations/systems. This is a persistent dilemma in terms of organizational change and technology adoption/acceptance
o need to bring IT org into the open source non-proprietary fold that uses other peoples ideas and code (issue is loss of control and trust)
• 1st gen – fast and loose and using public information
• 2nd gen – consumer grade and industrial strength (audit, authentication, etc almost has to become the responsibility of developer – may be an abstraction layer (?) that federates existing capabilities). Most certainly requires greater discipline in development to assure reliability, availability, security and performance to support enterprise needs not just a cool hacked function for an “enterprising” user.
o Unsure if the target is internal enterprise services or is it providing enterprise services across the web to external users – certainly could be both. o Need to provide a competitive advantage in the rich client environment in the absence of a network state, resource utilization/awareness – be context aware o Must give consideration to the idea that it will require SLA’s with API providers
• Enterprise issues that need to be addressed: pride of authorship - only use it if you are willing to lose it; authorization/audit; security; reliability; performance
o By and large many of these are not unique to mashups but universal to S/W apps/web services in general.
