I am a developer of software that queries banks' data (eg. ask
executors, tax burear etc. questions about clients property).
It is now uses in 16 banks. In most of them we integrate through "SQL
interface" - tables which are cache of canonicalized distributed data
(eg. 3 or more banking IS - accounts, safe boxes, credit card, stocks
and bonds...). Quite interesting and specific application from EAI view
;-) (integrate with all important IS)
Now we're transfering from database to web services and we face up
performance issues:
- replicating database takes at most tens of minutes (AS/400, 5 mil
rows) performed nightly
- answering one query takse 10-20 ms (eg. 3 inserst via INSERT INTO
... SELECT FROM ...)
- using web service against live system means (per query)
- WS call means
- WS encapsulates EJB
- EJB encapsulates COBOL
- COBOL read from more than one database
- for each query we have at least 5 WS calls over local network
(that's how WS usualy work when you have legacy systems)
Other benefits:
- using web services is not yet quite common practice, while using
databases is - every one knows SQL
- they can store derived fields that computes long time or it's
imposible to have it computed online - eg. last transaction on account
- you can do some trick that web services usually does not support -
like with *,?; seach by every column you want
But we view our tables as well defined interface between bank and our
application. It does not change between minor versions. Of course it
does between main version. The last version of application is independet
of tables structure (it could be used for queries over bank accounts, in
telecomunication company, insurance company etc.).
BI viewpoint:
You must have some DWH for BI, eg. DWH hidden behind services. Some
data cannot be computed online from other services.
Lukas
http://www.archaebacteria.net
>
> In the context of SOA-based "master data management", one can do
> parallel service invocations out to the "freshest data", certainly.
> But there are some areas where an ODS is still needed:
> - a persistent cross-reference
> - master key management
> - a cache of canonicalized distributed data
> - a store for derived and/or invented fields (such as those created by
> a cleansing process)
>
SPONSORED LINKS
| Computer software | Computer aided design software | Computer job |
| Soa | Service-oriented architecture |
YAHOO! GROUPS LINKS
- Visit your group "service-orientated-architecture" on the web.
- To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
