RESTful systems must consider security, separation of concerns, and legacy web services.
Build an API Security Ecosystem
Security is not an afterthought. It has to be an integral part of any development project. The same applies to APIs as well. API security has evolved significantly in the past five years. The growth of standards to date has been exponential. OAuth is the most widely adopted standard, and is possibly now the de-facto standard for API security. To learn more, read the Build an API Security Ecosystem white paper.
Promote Legacy Web Service Re-use with API Facades
RESTful APIs are a strategic component within your Service Oriented Architecture initiative. Many development teams publish services, yet struggle to create a service architecture that is widely shared, re-used, and adopted across internal development teams. RESTful APIs extend the reach of legacy web services. To learn more, read the Promoting Service Re-use white paper.
Converging RESTful API Strategies and Tactics with Service Oriented Architecture
While everyone acknowledges RESTful APIs and Service Oriented Architecture (SOA) are best practice approaches to solution and platform development, the learning curve and adoption curve can be steep. To gain significant business benefits, teams must understand their IT business goals, define an appropriate SOA & API mindset, describe how to implement shared services and popular APIs, and tune governance practices. To learn how REST and SOA coexist, read the Converging API Strategy with SOA white paper.