Roy Fielding talks to Mike Amundsen about versioning on the Web, why hypermedia is a requirement in his REST style, the process of designing network software that can adapt over time, and the challenge of thinking at the scale of decades.
This article, the first of a new series, examines APIs from a business perspective. It covers the importance of tying your APIs back to your business value, with examples from Amazon and Twilio. 2
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.
The book fifty quick ideas to improve your user stories aims to help people to write better user stories and support teams in iteratively delivering products that satisfy their customers' needs.
When you are dealing with a team of people who are separated from you, working together during project planning and recognizing that you both share the same concerns increases the chances of success.
Our understanding of SOA has changed over the last 15 years. We review and update the Principles of Service Orientation providing a more business-focused & less technology-specific perspective. 6
The book Improving Software Development Productivity contains practices, models and case studies which help you to quantitatively support adoption of agile software development.
Ganesh Prasad proposes separating governance and management in SOA projects to make sure that right dependencies are used throughout the system in order to promote agility and reduce costs and 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? 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