SOA is designed to build and maintain applications in an enterprise. Rather than designing applications from the ground up, SOA allows developers to reuse code between departments and combine resources from all over the company.
The repository holds information about dependencies and relationships between service components, preventing developers from breaking an application when they tweak one of the components.
A repository is similar to a Universal Description Discovery and Integration (UDDI) service registry. Both store information about services. But as enterprises start to implement SOAs, repositories increasingly are used for development purposes and registries to store information required to deploy them, BEA said in a conference call.
"The registry is more and more viewed as the place where end point information and interface definition and binding type policies are kept, which is distinctively separate from the rest of the information that is needed to look at things like analysis, and deployment type architectures," said Paul Patrick, chief architect of BEA's Aqualogic.
BEA already offers a registry and will maintain both its registry and Flashline's repository. The Flashline product will be integrated into BEA's Aqualogic SOA offering.
_(20).jpg&h=140&w=231&c=1&s=0)
_(26).jpg&w=100&c=1&s=0)
iTnews Executive Retreat - Security Leaders Edition
_(1).jpg&h=140&w=231&c=1&s=0)
