wRESTling with REST

I'm still struggling with the decision to create a REST or traditional web service. Over the weekend I started reading RESTful Web Services and I'm now thinking that a RESTful approach is very doable. Here are my thoughts:
  • REST resources are inherently stateless and shareable. All the information needed to reconstruct the view of a resource exists in the URI. Although I listed this a a "pro" before reading the book, I'm more convinced of the benefits now.
  • I had a concern about long query criteria in the URI, but I'm thinking of adopting the Ruby-like approach of referring to ids. The RESTful authors prefer a more human readable URI (as it is self documenting), but many of my filter criteria cannot be accessed through unique strings.
  • I believe I was trying to do too much at the beginning (not keeping it simple). My object relationships are complex, with most objects linked to several related (non-subordinate) lists of objects. I wanted to have a single interface with options to include specific subsets of data as well as page through the results.

    As I thought more about this, I began to think that these subsets should actually be separate URI requests. Clients will probably make more requests to the service for data, but underneath, my Ruby controllers were making multiple requests to the database anyway. Here I'm hoping that the additional overhead of multiple GET requests will be balanced by the simplicity and usability of the interface (and no SOAP overhead).

As I become more familiar with the concepts of REST, I'm getting more comfortable thinking of my objects in terms of URIs and resources opposed to RPC calls and parameters. It's kind of similar to the shift in thought from procedural programming to object oriented design.

Comments

Post a Comment

Popular posts from this blog

I Believe...

A recent reorg at my company left me with a new manager - and a different approach to software development than my team had been previously following.  Our new approach is one that I don’t necessarily agree with, but it led me to think about - and reevaluate -  those tenets of software development that I think are important and that I believe lead to increased quality and productivity. This post will consist of fairly high level discussions about how to organize code, teams, and projects - but contain very little actual code. Many of these ideas will not be my own.  They are mostly ideas I’ve learned from others and their willingness to share their experiences with me.  They are, however, ideas that I’ve practiced and hardened as I’ve worked to build my own ideal environment for delivering value through software . Many of these ideas I now take for granted as commonplace (even though they aren’t).  I felt a need to document them anyway - so people can unde...
Read more

More stuff to get excited about

Chrome OS I'm excited about Google's announcement to release what sounds like an ultra lightweight OS to basically surf the Internet. I'm hoping this device will allow me (and others) to breathe new life into old, underpowered laptops, allowing them to essentially work as netbooks. This could also open up new and inexpensive opportunities for schools to recycle or prolong the life of expensive computing equipment and expand horizons of their students. I've been watching the One Laptop per Child (OLPC) movement for some time and I see this as another avenue toward their goal. I don't share the optimism that this OS will somehow replace Windows. Sometimes you need extra horsepower and functionality. I edit a lot of photos and create some simple video, but the web tools I've tried to do either task can't hold a candle to the four-year-old version of Photoshop Elements I own. I'm not sure CPU intensive apps like this will port very well to the web....
Read more

A few quick notes

It's been a quiet few months. I haven't worked on too many things I've felt like writing about. That's not to say I haven't been busy. One thing I've been reading more about building great teams and delivering more to our customers. I'm just starting to read Creating Magic: 10 Common Sense Leadership Strategies from a Life at Disney . Obvious from the title, this book outlines the approach Disney teaches all of it's Cast Members (employees) on how to be great leaders and provide their visitors with great experiences. I've been wanting to read this for some time and I'll be sure to write more as I work my way through it. Some related blog posts I've enjoyed recently are: The Duct Tape Programmer from Joel on Software where he reviews a chapter of the book Coders at Work . The post basically talks about doing the simplest thing possible to get something out the door and into people's hands. Amen to that! I've also been enjoyi...
Read more