This is a single archived entry from Stefan Tilkov’s blog. For more up-to-date content, check out my author page at INNOQ, which has more information about me and also contains a list of published talks, podcasts, and articles. Or you can check out the full archive.

JAOO 2008: REST Patterns and Antipatterns

Stefan Tilkov,

I've uploaded the slides from my own talk at JAOO 2008 (warning: this is a 12MB PDF). As usual, not sure how much value they have on their own; YMMV.

On October 1, 2008 12:23 PM, said:

The hyperlinked PDF seems to be empty.

thanks in advance,


On October 1, 2008 7:56 PM, said:


as a matter of fact I found some of the advanced topics towards the end of the presentation to be very topical to our current problems. Send (modified) representation of a newly created resource back to the client along 201? Doh! Why didn’t I think of this sooner…

As usual - thanks for sharing. Congratulations on a nice talk.


On October 27, 2008 9:55 AM, zdck said:


I read your presentation/article and it contains good ideas and hints. But one slide with notice “Stop worrying about URI design” is contradictory with many other articles. According to me uri design in REST application is crucial. What did you mean this notice?

thanks for reply.

On October 27, 2008 10:11 AM, Stefan Tilkov Author Profile Page said:

URI design is a useful and reasonably complex discipline. It’s go nothing to do with REST, though: applications should discover URIs by means of hypermedia, i.e. through following links, and never “construct” them.

I don’t at all object to good URI design, and try to do it myself – I just wanted to point out that people tend to equate this with REST and spend way too much time on it instead of focusing on the more important stuff.