InfoQ Homepage Presentations Enterprise Integration Using REST: A Case Study
Enterprise Integration Using REST: A Case Study
Summary
Brandon Byars discusses the constraints and the flexibility of nonpublic APIs, and lessons learned from scaling RESTful integration across more than a dozen teams.
Bio
Brandon Byars is a technologist and principal consultant at ThoughtWorks. He has a wide range of experience in multiple technologies and business domains, with an interest in applying systems thinking to software development. Brandon has a particular interest in exploring the social and organizational aspects that allow software development to scale to large teams.
About the conference
Software is Changing the World. QCon empowers software development by facilitating the spread of knowledge and innovation in the developer community. A practitioner-driven conference, QCon is designed for technical team leads, architects, engineering directors, and project managers who influence innovation in their teams.
Community comments
I don't see the point of the REST Maturity Model
by Faisal Waris,
I don't see the point of the REST Maturity Model
by Faisal Waris,
Your message is awaiting moderation. Thank you for participating in the discussion.
As per my understanding, at HATEOS we should be agnostic of URI's, contracts and versioning. However if all we have is contracts and versioning to start with, what's the path to HATEOS?
Also REST does not even have the abstractions for reactive and asynchronous interaction which means we are missing a major component of contemporary application architecture.