|
RSS Feed
During a recent presentation that I made about mashups, two interesting questions came up. First, what is the connection between SOA and mashups. The second question was about the relevance of mashups and Web 2.0 technologies to the enterprise. I recently found several articles on these topics. John Hagel has a writeup that compares SOA to Web 2.0 and has pointers to many other blogs on the subject. Web 2.0 journal has a piece highlighting the user-driven nature of Web 2.0 being an impediment to enterprise acceptance. Two other blogs, one by Nick Carr and another by Andrew McAfee are good reads on the topic.
Comments (0 )
s
 During a recent presentation, participants were curious about why UPS was not occupying a key position. UPS has the best locational information that they get to validate on a daily basis. Will they lose out to a provider like Google that has "good enough" locational information?
Comments (0 )
s
In his article, It's the Ecosystem, Stupid, Diego Rodriguez points out the value of understanding your ecosystem and designing products and services based on that. In our own research we have shown that, within the software sector, companies that take into consideration complementarities for making M&A and alliance decisions perform better that those that don't (see www.softwareecosystems.com).
Comments (0 )
s
In the past week many press announcements were about stacks. Oracle saying that it is trying to have a presence in all layers and Marc Benioff saying that stacks are not relevant anymore. I agree with both of them:-)
First of all, stacks are just decomposition and layering of functionality. Do consumers care if all the layers of functionality are served by the same company? Is "one throat to choke" a real customer need? If we are concerned about just technical interoperability, we must care (some what) about getting all the layers of the stack from the same company. I say 'somewhat care' because with standards and APIs technical interoperability can still be accomplished under divided technical leadership. Business interoperability, on the other hand, is still a goal. Business requirements are hard to identify and agree upon and, hence, most products do not work together when pulled out of the shrink wrap. This is one reason we still have service companies and systems integrators. Stacks would continue to be relevant as long has we have uncertainty in business requirements. Once the requirements are well understood and non changing, integrated solutions (non-stack) will be more appealing.
Comments (0 )
s
There is a lot of talk around Oracle buying several Open Source companies. The latest being Novell. Two reasons are being provided for this. One, Oracle wants to own all the layers of the stack it provides to consumers. Once RedHat bought JBoss it became a new competitor by owning a similar stack. Meanwhile, IBM and MSFT are already strong competitors. Second, this is a pre-emptive strike. They feel that IBM or some other company will buy Novell.
My own opinion is that this is a bad idea. In theory, since Oracle’s products already work on top of Novell’s Linux distribution, ownership is not going to change anything. If they want to assure customers that their products would “work for sure” when purchased together, the existing alliances should suffice. What difference does ownership make if the APIs from Novell’s Linux distribution are open and standardized? In fact, by acquiring it Oracle may scare off other complementors that build on top of Novell’s OS. The whole point in the era of divided technical leadership is specialization and interoperability.
Comments (0 )
s
 GoogleMaps, Flickr and del.icio.us have the highest betweeness centrality scores.
Comments (0 )
s
Newsweek ran an article titled " The new wisdom of the web." They show with examples the transformation of the web from static content publishing to people generated dynamic content. The people generated dynamic content has moved from shots of a fish bowl and traffic lights to purposeful problem solving. This is being fueled by the arrival of mashups that allow reuse of preexisting services to create new ones (see NYT article Software Out There). Key companies to track are myspace.com, salesforce.com, flickr.com and Amazon's mturk.
Comments (0 )
s
Comments (1 )
s
This is one neat idea. It reminds me of the self service kiosks that airlines have created. We enter our data into the airline reservation systems, print out our ticket at home, scan our ticket into a kiosk to check in and pay the airlines for taking us from point a to point b. With google base, given its 60 million user base, realtors, auto-dealers, job seekers and other use the user interface to upload content, label/tag it and have it indexed by Google. We are already seeing many examples of this for jobs and real estate.
Comments (0 )
s
 AOL with over 200 APIs has entered the network.
Comments (0 )
s
Error sending email
Email sent successfully
|