Foreword
I’m an RPC guy in my bones. I spent years of my life working with various remote procedure call technologies, so when SOAP came along, it seemed like the obvious next step on this path. To me, web services meant SOAP, period.
Then REST appeared.
When the RESTful approach first hit the scene, I wrote a short article describing it. At the end, I noted SOAP’s broad support, then closed with this:
Still, even though SOAP is already quite well established, the ideas embodied in REST are worth understanding. Web services are still new, and REST makes a remarkably interesting contribution to the technology.
For a SOAP guy in 2002, I thought I was being quite open-minded. The REST fans didn’t see it this way. My inbox sizzled with mail telling me that I was stupid for not immediately seeing REST’s innate superiority over the pure evil that was SOAP.
My response was to completely ignore REST for the next several years. I didn’t write about it, I didn’t speak about it, and I wouldn’t even take questions on the topic during talks on web services. I was convinced that REST was the religion of a small band of fanatics, and rude ones at that. The common appellation for a REST fan—RESTafarian—seemed very appropriate to me, derived as it was from the name of an actual religion. These people were true believers, and I couldn’t share their faith.
Yet REST was too cool to ignore forever. Once you get your mind around the approach (which doesn’t take long—it’s ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access