Abstract
Managing a Service Oriented Architecture (SOA) requires a well-defined model of what a service actually is, and a structure within which services can be published, documented, and consumed. Without such a definition and organizational structure, it is hard to reap the benefits of a SOA. This paper presents a case study that is closely aligned with how the Web is organized as a SOA, but adds some structure so that service producers and service consumers can be supported in their goals. Using this approach, it is possible to realize the architectural benefits of a RESTful architecture, but can still make sure that the published services follow a set of guidelines and constraints that the SOA is based on.
About the author
Erik Wilde studied Computer Science in Berlin, received his Ph.D. from ETH Zürich in Switzerland, and worked for 5 years at UC Berkeley's School of Information as Associate Professor. He joined EMC in 2011, where he now works as an architect. His main responsibility is to provide guidance and support for the transition from a product-oriented portfolio to a service-oriented one, where one of the main aspects is a firm commitment to REST as the architectural style.
EMC, Koll Center Parkway 6801, 94566 Pleasanton, CA, USA,Tel.: +1-925-6006244
©2014 Walter de Gruyter Berlin/Boston
