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.
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.
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. 1
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. 13
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. 12