Following the online webinar "Exploring the Uncharted Territory of Microservices" organized by XebiaLabs, which we covered in The Benefits of Microservices, Randy Shoup and Andrew Phillips answered a number of questions on microservices asked by participants.
In this article, authors provide an overview of current SOA technologies and how to evolve in legacy environments. They also discuss the topics of SOAP vs. REST web services, Enterprise Application Integration and incremental transition to SOA in legacy environments.
Roy Fielding talks to Mike Amundsen about versioning on the Web, why hypermedia is a requirement in his REST style, and the process of designing network software that can adapt over time. 14
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. 1
This series takes the reader on a journey from determining the business case for APIs to a design methodology, meeting implementation challenges and maintaining public APIs on the Web over time.
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? 2
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.
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
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. 10