|
On the Mark: Tread Carefully in SOA Design
|
|
Marty Moseley worries that you’ll make a mistake in your service-oriented architecture development, one that puts data quality at risk. The chief technology officer at Initiate Systems Inc. in Chicago says SOA designers often retain elements of existing programs, such as Oracle tables. If so, you’re using SOA “just to schlep data around” in existing formats (perhaps perpetuating bad data) and making it harder to update information. Some try to get around this problem by creating a big, central master data service. Moseley shudders at this approach because it cripples real-time performance, hampers scalability and risks putting bad data in one place for all to share. “It’s a major fault in people’s thinking” about SOA development, he claims. According to Moseley, by deploying multiple master data services (such as those Initiate provides) for each SOA service, you improve performance and scalability while boosting data quality. And it’s on data quality, he says, that SOA apps will ultimately be judged.
|
 |
|
Read entire article on Computer World
|
|
|
Posted: Monday, November 26, 2007
|
|
|
|
