Skip to main content

Web 2.0 For Dummies - part1: WOA

I presented in a conference of mixed audience: IT professionals and non IT professionals. The topic was: Web 2.0: The New Internet generation.



The presentation was an introductory: describing and experiencing by navigating through examples of Web 2.0 services and discussing their attributes and the cultural and technological differences between them and traditional IT companies and products as well as Web 1.0 services and product. As SOA is the major topic of this blog, I am discussing the links between SOA and Web 2.0 before posting the rest of the presentation. The main links between SOA and Web 2.0 are as follows:



  • Mashups and Services share the same vision: non-IT people assembling services for creating an application.
    The results are Reuse of these services, Agility and fewer resources in comparison to previous Application Development methods. It should be remembered that assembling Services in an Enterprise or Virtual Enterprise context requires robustness, control and management. These requirements are not part of the Social Context of Web 2.0.

  • Web 2.0 technologies are used as part of Enterprise SOA architecture
    Technologies like Ajax, REST and Wikis are used in enterprises including enterprises transforming their architecture to SOA. This usage is reflected in the SOA architecture.

  • End Users (Consumers and Service Assemblers) User Interface patterns used in SOA architecture should be the same patterns used in these users Social interactions which are changing gradually towards Web 2.0 Rich Internet Applications (RIA) patterns and User Interface. Therefore the SOA Enterprise includes the robust managed and governed Service side, which should be integrated with the user friendly, easy to build Consumer and Services Assemblers side. The integration is established by using middleware which should link between these two totally conceptually different components. This task is quiet difficult. Leading Integration infrastructure vendors and startup companies are in the beginning of development of these new middleware solutions.

  • Web 2.0 Services and Communities as a Distribution Channel
    SOA includes common Distribution Channel and End User devices architecture, enabling independence between the Consumer end and the Service. However, Web 2.0 communities are conceptually and technologically distinguished from other channels.
    Advertising and presenting SOA vendor technologies in Web 2.0 sites


  • Vendors develop Innovative concept of advertising SOA products and solutions in Web 2.0 communities.


SOA related slides appearing in my presentation are appended to this discussion. Next posts will include the other slides included in the presentation in sequential order. Each group will be appended to a discussion of its subtopic.














Labels:

Comments

Post a Comment

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  ...
16 comments
Read more

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 ...
11 comments
Read more

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...
8 comments
Read more