How is an SOA architecture really supposed to be implemented?
Posted
by smaye81
on Stack Overflow
See other posts from Stack Overflow
or by smaye81
Published on 2010-04-19T03:17:29Z
Indexed on
2010/04/19
3:23 UTC
Read the original article
Hit count: 220
My project is converting a legacy fat-client desktop application into the web. The database is not changing as a result. Consequently, we are being forced to call external web services to access data in our own database. Couple this with the fact that some parts of our application are allowed to access the database directly through DAOs (a practice that is much faster and easier). The functionality we're supposed to call web services for are what has been deemed necessary for downstream, dependent systems.
Is this really how SOA is supposed to work? Admittedly, this is my first foray into the SOA world, but I have to think this is the complete wrong way to go about this.
© Stack Overflow or respective owner