As with many development decisions the buy-vs-build decision needs to be answered first. There are several important issues to remember if you choose to build your own SOA instead of buy. These same issues also are helpful to those evaluating an SOA to purchase.
A service-oriented architecture needs to provide the infrastructure that allows for service-oriented development. This focus of building the service first and then connecting the user interface and data connectivity allow for the business logic that is the service to be reused across applications. The SOA allows the services to be:
- protocol independent
- location transparent
The SOA allows for services to be registered, which can then be located and called. The discovery of services and connectivity to them should be in such a way as to allow the enterprise application to be deployed according to the requirements of the application. This means that the SOA should provide the ability for the requester of the service and the service itself to be on the same tier or accessed remotely. This ensures the protocol independence and location transparency required of the SOA.
As you look to build your own SOA you need to build the infrastructure that allows for registration, discovery, and calling of services in such a way that facilitates development of the enterprise application without the need to consider the specifics of how it might be deployed. This ensures the application will continue to meet the business needs even as possible usage increases.
Dig Deeper on Topics Archive
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.