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.
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.
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.
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
The n+1 one problem doesn’t just affect ORMs, any kind of Web API can suffer from the same performance problems. Ali Kheyrollahi discusses some of the ways to identify and correct n+1 scenarios.
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. 8
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. 2
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.
Micro Sun describes some of the techniques Tencent use to scale Qzone, a social networking platform in China with over 600 million monthly active users.
Reza Shafii explains how to satisfy two fundamental needs of API design and implementation, as defined by the API hierarchy of needs, with RAML, API Designer and APIkit.
We demonstrate how to build a RESTful API on top of CQRS systems. The result joins HTTP semantics and REST style with distributed computing concerns such as eventual consistency and concurrency. 4
This article will take you through creating a simple RESTful web service with Spring Boot and Aerospike, a distributed and replicated in-memory NoSQL database.