If we look on any of enterprise standards, we always find that enterprise are presently accumulated with lots of software made up of new and old architecture, tightly integrated with each other and dependent on specific platform. If we look at the history of architecture, earlier in 1980s, most of the architecture was monolithic and there was no need to concentrate on the integration part of the product. At that time, if the product is doing the desired task, it was treated as the good software. But as soon as market changes and so technology too, company then look for some more loosely coupled architecture. There comes the magic of client/Server and then 3-tier, N tier and also distributed components. Object Oriented was really helpful in solving the problems of day today applications and making the life easier for the developers. One of the basic problems with Object oriented design is to modelling the application interaction. Presently the need of the market for the software is something like pluggable components, which can be changed according to market needs, business trends or on company’s needs there was a need of loosely coupled architecture and this is where Service oriented architecture comes into the scene. Reusable application components will continue to find new clients that will need to consume them. In the past, component-based code reuse would suffice, but in most companies today the need for cross-platform reuse makes any proprietary strategy very short-sighted. The constant need for agility, platform independence, and return on investment (ROI), and multi-client capabilities will continue to drive any enterprise to service-oriented design.
To be continued …
No comments:
Post a Comment