InfoQ Homepage SOA Content on InfoQ
-
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.
-
Apache Kafka: Next Generation Distributed Messaging System
Apache Kafka is a distributed publish-subscribe messaging system. This article covers the architecture model, features and characteristics of Kafka framework and how it compares with traditional messaging systems.
-
Web APIs and the n+1 Problem
The n+1 one problem doesn’t just affect ORMs. Any kind of Web API, RPC/Web Service or RESTful, can suffer from the same performance problems. In this article, Ali Kheyrollahi discusses some of the common scenarios that lead to n+1 in web APIs and ways to correct them.
-
Microservices: Decomposing Applications for Deployability and Scalability
What are microservices? This article describes the increasingly popular Microservice architecture pattern, used to architect large, complex and long-lived applications as a set of cohesive services that evolve over time.
-
Restify and Mobilize Your Data
Val Huber explains creating a RESTful API from an existing database schema, extending the API to define multi-table hierarchical resources, and adding behavior using declarative reactive expressions.
-
Russ Miles on Antifragility and Microservices
Currently, Antifragility and Microservices are trending topics and this might be a hint that there are new architectural paradigms or design patterns on their way for building application systems.. We're discussing these new concepts with Russ Miles to find out what they are good for and how to apply them in an architect's or developer's daily business - for existing applications and those to come