Thursday, September 10, 2009

Resource-oriented architectures (Beautiful Architecture - Chapter 5)

Perhaps it is due to not having an overly abundant amount of experience with modern web query concepts, but some of the information either bored me to tears or caused me to doze off. Well, some of that could be from lack of sleep this week...The paper seems like a nice scapegoat.

Even though it wasn't stressed succinctly, part of the information presented has been passed down over generations to computer scientists -- don't break the interface. When interfaces change, you need to be able to support previous versions of the interface in order to keep communication flowing and not break other external systems. Changes to logic "behind-the-scenes" should be transparent to users once the interface is established.

I do respect the idea of being able to have different formats of the data returned for a request. Technology is evolving and the respective layout of data will vary on whether or not you are using a computer, PDA, iPhone, or Commodore 64 emulator. The user appreciates the multiple options and not being tied to a specific presentation device.

REST utilizes four verbs: GET, POST, PUT, and DELETE. The messages types present a simple interface for developers. Simple is good. As one of my classmates recognized, I also appreciate the similarities to using SQL for select, insert, update, and delete.

No comments:

Post a Comment