If you’re just joining this article series, it is one aspect of a response to the gap between how development and how operations view technology and measure their success – it is wholly possible for development and operations to be individually successful, but for the organization to fail. So what can we do to better align development and operations so that they can speak the same language and work towards the success of the organization as a whole? This series attempts to address a portion of this problem by presenting operation teams insight into how specific architecture and development decisions affect the day-to-day operational requirements of an application.

This article is the second part of a two-part installment on Service-Oriented Architecture (SOA) and the impact of SOA on operations and DevOps. The first installment reviewed the Simple Object Access Protocol (SOAP) and the challenges that operations faces when managing a SOAP application. This installment reviews the other leading SOA technology: REpresentational State Transfer (REST). SOAP and REST behave differently and have their own management challenges and this article will help you better understand those differences and specifically how they affect the production operation of each.

Read the rest of the article at about:virtualization