InfoQ Homepage SOA Content on InfoQ
-
Making the Case for an API Roadmap
Chris Haddad explains why one should create a roadmap for an API, providing advice on avoiding common API pitfalls, creating business value and monetizing API assets.
-
Article Series: Web APIs: From Start to Finish
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.
-
Updated Principles of Service Orientation
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.
-
How SOA Governance (and SOA Management) Should Actually Be Done
Ganesh Prasad proposes separating governance and management in large SOA projects to make sure that right dependencies are used throughout the system in order to promote agility, lower operating costs and reduced operational risks.
-
Sam Newman: Practical Implications of Microservices in 14 Tips
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? At last GeeCon 2014 in Krakow, Sam Newman tried to answer those questions by giving 14 tips about how microservices can interface, how the can be monitored, deployed, and made safer.
-
Why Some Web APIs Are Not RESTful and What Can Be Done About It
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?
-
Why SOA Should Be Viewed As “Dependency-Oriented Thinking”
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.
-
ARM Yourself for Enterprise Application Development
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.
-
Apache CouchDB: The Definitive Introduction
Apache CouchDB is an open source 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 and why it is different from all other databases.
-
Virtual Panel: Convergence of SOA Governance and API Management
There's recently been a lot of discussion about the convergence of SOA Governance and API Management. Services and APIs appear to deal with similar concerns, but historically the approach & philosophy has been different. Is there convergence and how? InfoQ spoke to a panel of SOA Governance and API Management experts to garner their views.
-
SOA and API Schism and Unification
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. They often promote a deep and divisive schism between pragmatic REST APIs and SOA. The division inhibits cleanly integrating SOA services and RESTful APIs into a unified architecture.
-
Converging API Governance and SOA Governance
Achieving Service Oriented Architecture initiative success requires creating loosely coupled consumer-provider connections, enforcing a separation of concerns between consumer and provider, exposing a set of re-usable, shared services, and gaining service consumer adoption. Many development teams publish SOA services, yet struggle to create a service architecture that is widely adopted.