Identification of REST-like resources from legacy service descriptions

Athanasopoulos, M; Kontogiannis, K

dc.contributor.author	Athanasopoulos, M	en
dc.contributor.author	Kontogiannis, K	en
dc.date.accessioned	2014-03-01T02:46:50Z
dc.date.available	2014-03-01T02:46:50Z
dc.date.issued	2010	en
dc.identifier.issn	10951350	en
dc.identifier.uri	https://dspace.lib.ntua.gr/xmlui/handle/123456789/32879
dc.subject	Migration	en
dc.subject	REST	en
dc.subject	Service-oriented systems	en
dc.subject	Software architecture	en
dc.subject.other	Accessing data	en
dc.subject.other	Architectural style	en
dc.subject.other	Legacy data	en
dc.subject.other	Legacy services	en
dc.subject.other	Migration	en
dc.subject.other	Remote Procedure Call	en
dc.subject.other	Representational state transfer	en
dc.subject.other	REST	en
dc.subject.other	Service Oriented Systems	en
dc.subject.other	Uniform resource identifiers	en
dc.subject.other	HTTP	en
dc.subject.other	Reverse engineering	en
dc.subject.other	Software architecture	en
dc.subject.other	Service oriented architecture (SOA)	en
dc.title	Identification of REST-like resources from legacy service descriptions	en
heal.type	conferenceItem	en
heal.identifier.primary	10.1109/WCRE.2010.31	en
heal.identifier.secondary	http://dx.doi.org/10.1109/WCRE.2010.31	en
heal.identifier.secondary	5645561	en
heal.publicationDate	2010	en
heal.abstract	Service-oriented systems mainly follow two principles for accessing data and invoking back end applications: Remote Procedure Calls and Message-Orientation. However, a number of researchers and practitioners have criticized these paradigms as too complex and rigid. Instead, Representational State Transfer (REST) architectural style has lately gained significant attention as an alternative means for accessing services and data. RESTful HTTP systems depend on Uniform Resource Identifiers (URIs) to uniquely identify and denote data and services as ""resources"". In this paper, we discuss a technique to analyze the descriptions of legacy data and services in order first, to model their roles and relationships and second, to use the discovered dependencies for extracting Unique Resource Identifiers and the available HTTP methods, so that these legacy service elements and data can be accessed using lightweight requests. © 2010 IEEE.	en
heal.journalName	Proceedings - Working Conference on Reverse Engineering, WCRE	en
dc.identifier.doi	10.1109/WCRE.2010.31	en
dc.identifier.spage	215	en
dc.identifier.epage	219	en