Bookmark and Share

Monday, 2 June 2008

Lightweight or Enterprise Grade?

There has been a lot of talk around mashups and SOA recently, and how they do or do not fit together. One view is that mashups enable IT to visualize the SOA to the business. Another is that mashups have no place in the enterprise due to the lack of governance over what gets built, how it gets built, and who gets to use it.

In an ideal world, one would be able to provide a face to SOA in a controlled manner, a UI that has all the good things of a service: discoverable, manageable, secure, whilst providing the consumer with the ability to modify and recombine pieces of this UI as they see fit. At Corizon we have built precisely this capability: the UIService. A UIService implements a lightweight RESTful interface which provides structured access to UI elements, extending the SOA pattern to the UI:

  • enables service producers to provide a UI with their business services
  • enables service consumers to discover, consume, modify and mashup the pre-built UIs
  • provides central IT with the required control
The UIService is the ideal marriage of lightweight technology and enterprise grade capabilities. To learn more about them, see http://www.corizon.com/Products/ui_services.php .

2 Comments:

  • At 16 June 2008 at 22:02 , Anonymous Anonymous said...

    Why do you need this extra layer of complexity and the extreme issues to retrain resources on a new set of tools? Seems a bridge too far.

     
  • At 18 June 2008 at 14:38 , Blogger Edwin van der Sanden said...

    UI Service enabling your UI development only requires a small amount of extra work, and can be done from within the popular Eclipse IDE. This small amount of effort will then lead to an architecture in which distributed UI Services are be composed in real time, into user centric application.

    This approach has many advantages over the traditional component based reuse, e.g. the owner of the Payment UI Service can update its UIService implementation, which will be reflected immediately in all the consumer compositions, and won’t require modifying, building and deploying all application that include Payment functionality.

     

Post a Comment

Links to this post:

Create a Link

<< Home