From my experience, manipulating a CRUD layer from a RIA is simple.
The more difficult aspect, especially in a mashup, is performing
transactional tasks across this CRUD layer. For example, if you need
to update two systems simultaneously, then, today, the model falls
apart unless you own the entire infrastructure and can generate the
transaction inside the CRUD layer.
__________________________________
JP Morgenthal
President & CEO
Avorcor, Inc.
46440 Benedict Drive
Suite 103
Sterling, VA 20164
(703) 444-1130 x 4: Office
(703) 554-5301 : Cell
[EMAIL PROTECTED]
__________________________________
SOA success is just a click away...
On May 14, 2007, at 7:09 AM, Ashish Deshpande wrote:
--- In [email protected], Michael
Poulin <[EMAIL PROTECTED]>
wrote:
>
> In the Presentation layer, user experience is not bound any more
to the fragmented web
pages and page flows running exceptionally in synchronous mode; in
the Business layer,
there is no need for special components but only services; in
between layers, there is no
need any more or traditional Web application' facades, adapters,
etc.) but just data
transformation and service subscription utilities. Data
transformation is bi-directional:
from/to the Business Interfaces/User interface format to/from
business services'
interfaces format. That is, Web apps shrink into data
transformation facilities.
Exactly – most real web applications boil down to CRUD operations
on documents. And
web services tend to expose these operations on documents or
combinations thereof (a
business process or service). What's missing is an easy way to
interact with these
documents using Rich Internet Applications (RIAs). That's where
Ajax comes in – it puts a
"face" on SOA and makes it possible to create complex, visual,
browser-based applications
by mashing up web services on your network. Just imagine
replicating the mashup
phenomenon within your company – even just within the IT department.
> JP Morgenthal <[EMAIL PROTECTED]> wrote: You don't need SOA for
RIA. You just need a Web Service. Web Service does not equal SOA.
You can use Web
Services without any forethought as to reusability. In fact, if you
read my blog entry on
the matter (www.avorcor.com/morgenthal) you will see that I had to
mediate a well-
designed SOA with an XML server pages facade just to simplify the UI
Sure, you can use any service and as I said I tend to use REST but
that's neither here nor
there. From my experience with clients (these are mostly intranet
applications inside
businesses), <strong>the web application boils down to a user
interface performing CRUD
operations on documents</strong>. The question for me is: is this
indeed the case and, if
so, how easily can users create RIAs that manipulate these documents?
Thx,
-Ashish
