Skip to main content

Web 2.0 For Dummies - part3: Background

This post is the third post in the "Web 2.0 for dummies" posts, based on my Web 2.0 presentation in a conference.


In year 2000 there were three leading operating systems families:
Mainframe - The most robust and scalable platform, which was able to execute heterogeneous workloads, UNIX and Windows. The third was the least mature and the least scalable and robust platform. As an experienced expert in IBM Mainframe operating system, I was able to identify Windows 2000 Data Center weaknesses and to think of an add-on product for overcoming some of Windows' limitations. The theoretical solution targeted both Data Centers and Web. I applied to a Seed Venture Capital which checked the document describing the problems and the proposed solution.
The Venture Capital rejected my start up proposal. The only reason for immediate rejection was: "It is not pure Internet solution" i.e. the reason for rejection was possible applicability to Enterprises Data Centers.
I am not arguing that the rejection was false (I checked other start ups ideas for Venture Capitals before my start up proposal. The first question I would ask someone applying with similar idea to mine would be: Do you have access to the Windows operating system source code? I probably would reject the startup idea in case of a negative answer), I am just describing the Dotcom over Hype or illusion prevailed in those Web 1.0 or Dotcom days.


Unsurprisingly, the Dotcom failed or collapsed (that was the reason for choosing the YouTube Domino Fall Down clip to be included in my previous post The taste of Web 2.0).
The fall of Web 1.0 enabled the Web 2.0 phenomena as described in the following images and text.








In year 2001 DotCom collapsed. Many DotCom companies disappeared or shrank dramatically. However, not all Dotcom companies were harmed significantly.



The companies appearing in green in the image above were not harmed significantly by the DotCom collapse.
For example, Google was established in 1998 and still succeeding.
The companies appearing in red were harmed significantly by the DotCom collapse.


The silde above hughlights the key questions discussed in that brainstorming.


The last bullet depict an example of historical new generation: Software Centered model instead of Hardware Centered model. Some companies did not survive the model change. The most known example is Digital one of the biggest players in the computers industry.


O’reilly is a company which publishes books and e-books and organizes conferences. The participants in this brainstorm were O’reilly experts (including Dale Dougherty the creator of this term) and MediaLive employees.



Netscape is the representative case of Web 1.0 companies.
Its business model is similar to business models of non-Web infrastructure software companies. The company was acquired by AOL prior to the DotCom collapse of 2001
The following images present the classical representative of Web 2.0: Google. The differences between their model and the classical software vendors model as well as Netscape model can be found easily.


The image above highlights Google model.
The main concept is the Web as a Platform model. No platform control wars as in NetScape model, but adapting to Web infrastructure technologies.
The bullets or parts of bullets marked in red relate to concepts deviating from traditional software vendors' model.
Page Rank is a Recursive Mathematical Algorithm developed by Larry Page as a student in Stanford University. The idea is to assign rank to a page during a search. The rank is based on weighted index. The index takes into account two factors: the number of references to that page and importance.
.
Open Social API is a new initiative by Google for common Application Programming Interface (API) accessing Social Networks and communities' sites.
MySpace, Linkidn, Bebo, Plaxo and Orkut joined to Google.
Non-pure Web 2.0 vendors Oracle and Saleforce.com also joined.
The forth post will describe the ideas, concepts and models of Web 2.0.

Comments

Anonymous said…
Similar to many organizations, the La - Porte County IT department must
accommodate and support many different departments, each with
a variety of document and record management needs.

In taking close up shots, you can make your subject sharp (not blurred) and
your background blurred. There's a time for that, but the actual writing
needs to be separated.

Popular posts from this blog

The mainframe: still alive and kicking

Recently, I was interviewed by  Pcon   (unfortunately the link points to an Hebrew only site) as part of debriefing on Legacy Systems.  Pcon is an Israeli company investigating IT topics by quoting professional articles and interviewing experts. They publish the results of the investigations including practical recommendations. This post is mainly about topics raised by me during the interview, but not included in the debriefing, which will be published.    What are Legacy Systems? The term Legacy Systems refers to old application systems and/or veteran technologies still in use.  Usually, the term Legacy Systems is associated with: 1. Mainframe Hardware e.g. IBM System z and its Operating Systems or Proprietary Servers and Operating Systems such as HP Alpha and OpenVMS Operating System, IBM AS/400 and OS/400   Operating System. 2. Development and Production Environments, e.g. COBOL , Natural and DBMS systems such as Adabas  ...

Will Business and IT Aligned?

For decades we are talking about closing the gap between business and IT , but the gap is still as wide as it was. In the beginning of the ERP era, we focused on aligning Business Processes and Core Systems, but in most enterprises we failed. SOA was the next alignment promise: defining the SOA Services in Business boundaries instead of Technical boundaries, should narrow the gap. However, despite of SOA Business Value ( Agility and Reuse )  in most enterprises,  the large Business-IT Gap remained as large as it was.  The IT Community aimed at the next alignment attempt: SOA is technical and BPM is its Business related complement.  Will the current BPM based alignment attempt succeed? I do not know, but Nick Heath's article  titled: Stop doing what the vendors tell you, CIOs told , published in  Tech Republic , suggests that the root of the problem is not Technological .   Stop Doing What the vendors Tell You Nick Heath's article is based ...

Vendors Survival: Will Software AG Survive until 2019?

This post is another post in the Vendors Survival series following posts on Microsoft , Google , HP , Sun and EMC . On July 14 th Software AG and IDS Scheer announced that Software AG is going to take over IDS Scheer . The intended acquisition is an opportunity to add another post in my Vendors Survival posts series. A brief history of Software AG Mainframe products Software AG is larger than any German software company except SAP . It was established in the Mainframe age (in 1969). I worked with many customers, who used and some of them are still using, its two flagship products Adabas and Natural . Although these products support many platforms, their main platform is IBM Mainframe. Adabas is a database and Natural is a development environment. Like other pairs of Database and Development Environment in the mainframe environment (e.g. Ideal and Datacom , Mantis and Supra) build by the same vendor, they are tied together. As a result, although it is possible t...