This series takes the reader on a journey from determining the business case for APIs to a design methodology, meeting implementation challenges, and taking the long view on maintaining public APIs on the Web over time. Along the way there are interviews with influential individuals and even a suggested reading list on APIs and related topics.
Our understanding of SOA has changed over the last 15 years including new aspects such as Service Execution Context and a re-defined notion of the Service Contract. This paper reviews and updates the Principles of Service Orientation based on the first OASIS SOA RAF standard bridging the gap between business and technology and eliminating technology-specific wording in their formulation.
Ganesh Prasad proposes separating governance and management in SOA projects to make sure that right dependencies are used throughout the system in order to promote agility and reduce costs and risks.
What are the practical concerns associated with running microservice systems? And what you need to know to embrace the power of smaller services without making things too hard? 1
Many Web API designers claim their are RESTful, but their APIs have little in common with REST. What can be done to make a web service API truly RESTful? 8
Ganesh Prasad proposes minimizing service dependencies in a SOA implementation rather than avoiding point-to-point connections in order to obtain a more flexible system that can evolve over time.
Enterprise Application Development can be smartly standardized in order to take advantage of existing code and component based architecture. Mark demonstrates an approach to clarify this EA pattern. 6
Apache CouchDB is a Document NoSQL database that uses JSON for storing documents. In this article, Jan Lehnardt gives an overview of CouchDB, its architecture and what problems it aims to solve. 3
There's recently been a lot of discussion about the convergence of SOA Governance and API Management. InfoQ spoke to a panel of SOA Governance and API Management experts to garner their views. 1
While both API and SOA have similar business and technical goals, many API proponents continue to describe APIs as a significantly different approach with little connection to SOA. 1
Many development teams publish SOA services, yet struggle to create a service architecture that is widely shared, re-used, and adopted across internal development teams. 1
Apache Kafka is a distributed publish-subscribe messaging system. This article covers the architecture, features and characteristics of Kafka and how it compares with other messaging systems. 11