Posts Tagged ‘SOA’

In my latest post, I wrote about the Service Oriented Architecture, in this one I will mention about API and the differences between the SOA and the API. They look nearly the similar but let’s have a deeper look.

Each of them is designed for a specific purpose; the SOA is used to make your code more efficient, and organized.

For the SOA, those who are looking forward to integrate some maps in their applications, it is so hard to design a map from scratch however it is easier to integrate a third party in the application and consuming its service.

SOA offers a number of functions that can be used and reused by the consumer as much as it takes. For the service builder, the SOA helps you build services that can be consumed by different platforms

The API is used to add more capabilities to the main application. For example the Facebook has APIs so developers can develop their apps based on Facebook platform.

The developers are using the API for using some data already existing in the database, so the application can be used for retrieving data, it doesn’t depend on certain functions.


If you are a developer you will certainly hear a lot about SOA (Service Oriented Architecture). So what is this? Let me get it the most important part a developer, it is a concept or you can use the services or code that someone else wrote, In other words you don’t have to write the whole program from scratch, you will consume other’s programs or services already built. Certainly that helps people a lot, it helps you save time, effort and money, let me give you an example when you integrate Bing’s map in your application, all you have to do is to add the services in your application as service reference if you are using visual studio and if not, it will take more effort adding the URL, however you will be able to consume the service, its functions and you may reuse them as long as you need.

This was the simple explanation for the SOA from the point of view of a developer; let us go a little deeper. Any SOA mainly depends on 2 things WSDL: Web Services Description language for describing web services and how developers can access these services and the second thing is the SOAP protocol to describe the communications protocols. The WSDL is a normal XML file mainly contains all the required information to invoke the web service. The SOAP protocol is simple XML-based to let applications exchange information over HTTP.

Most of the SOA available are web-based but that doesn’t mean that all the SOA must be web-based other can be hosted in apps.

How the SOA can help you in developing an application? As I said before in the beginning of the post, it helps you saving time, efforts and money, however this is not all. The interoperability is also one of the biggest advantages of the SOA. It helps you build applications on several different platforms consuming the service; these platforms no matter what programming language are written with, no matter what platforms they are built on, they can read the SOA and consume the service and may reuse the code as much as it needs.