Software Development Using Service Syndication Based on API Handshake Approach between Cloud-Based and SOA-Based Reusable Services

Software Development Using Service Syndication Based on API Handshake Approach between Cloud-Based and SOA-Based Reusable Services

Vishav Vir Singh
Copyright: © 2012 |Pages: 22
DOI: 10.4018/978-1-4666-0897-9.ch006
OnDemand:
(Individual Chapters)
Available
$37.50
Current Special Offers
No Current Special Offers
TOTAL SAVINGS: $37.50

Abstract

Reusability in the software development realm is a momentous cornerstone in deciding the success of an organization. The quantum leap in reusability was provided by object-orientation, which fundamentally altered the manner of thinking of software architects. The notion of the object and the installation of reusability as one of the central tenets is a critical requisite. Components that represented bigger and better software aggregates easily utilized by businesses to gain instant execution for their business services have made great strides. This gave way to the ultimate notion of a service which took software aggregates in components to fine and sharpened streams of software execution called services. This has been another inflection point in the overall curve of reusability, and most importantly, in agility and turnaround time for software production. The notion of services mandated the birth of a secure and trusted public interface to a service, which is called the Application Programming Interface (API). APIs represent a directory of services that a given enterprise offers.
Chapter Preview
Top

Background

History serves as a great guide when it comes to understanding the current ecosystem of technologies and architectures. It also serves as a great bread-crumb trail to understand how the evolution of computing paradigms occurred and the motivations and justifications of arriving on these decisions.

We had one computing paradigm revolution after the other initiating with the object-oriented programming model followed by the component-oriented software which led the basis of how code can be reused in a technology independent way. In succession to this came the notion of a service, which was a lightweight and highly maneuverable pathway of functionality that could be driven to serve any heterogeneous software problem domain by its reusability and syndication. Software architectures that were built around this core of a service became known as Service-oriented Architectures.

Complete Chapter List

Search this Book:
Reset