APIs and service do have a very direct and 1-1 relationship: an API is the interface of a service. However, what is different is that one's about the implementation and is focused on the provider, and the other is about using the functionality and is focused on the consumer. The service of course is what matters to the provider and API is what matters to the consumer.
Is API another a new sexy term for "Service"? Read Sanjiva's blog to find out more.
|
Date: Wed, 29th Aug, 2012
Level:
Intermediate
Reads: 504
Discuss this article on Stack Overflow
|
|
|
|
Sanjiva Weerawarana
CEO
WSO2 |
|
|
|
Services: If you build it will they come?
One of the most common anti-patterns of SOA is the one service - one client pattern. That's when the developer who wrote the service also wrote its only client. In that case there's no sharing, no common data, no common authentication and no reuse of any kind. The number one reason for SOA (improving productivity by reusing functionality as services) is gone. Its simply client-server at the cost of having to use interoperable formats like XML, JSON, XML Schema, WSDL and SOAP.
Read more on Sanjiva's blog.
