Archive for December, 2009

When should I start a REST initiative

Posted on 21. Dec, 2009 by guilhermesilveira.

1

Restfulie’s release, centered on hypermedia support, got a lot of attention back to not letting go the HATEOAS idea and the old question arrives again: is it worthy to invest money or time building a fully REST system in my company? A full REST architecture imply in many choices that some prefer to leave out, [...]

Continue Reading

Transactions do not exist in a Restful world…

Posted on 17. Dec, 2009 by guilhermesilveira.

7

Due to the last posts on infoq related to Restfulie, my work at Caelum Objects involved a presentation at one client, “Beginning a REST initiative” (based on Ian’s work) and the question came up: “but how do I control transactions without a custom software stack to help me?” The answer was, “you do not need [...]

Continue Reading

Hypermedia and dynamic contracts: let my bandwidth rest!

Posted on 10. Dec, 2009 by guilhermesilveira.

10

“Break it” to scale! Many systems contain webpages that are very similar to user “custom pages”, where they can configure what they want to see, and every piece is aggregated from different sources into one single page. In some cases, those are widget based frameworks as wicket and gwt that can be added to my [...]

Continue Reading

Hypermedia: making it easier to create dynamic contracts

Posted on 08. Dec, 2009 by guilhermesilveira.

4

The human web and christmas gifts You have been buying books at amazon.com for 5 years now: typing www.amazon.com in your browser, searching for your book, adding it to the cart and entering your credit card information. But this year, on December 15th 2009 something new happens. Amazon has launched an entire new “christmas discount [...]

Continue Reading

RESTEasy: Where did the hypermedia go to?

Posted on 03. Dec, 2009 by guilhermesilveira.

15

Some friends have asked what are the major differences between Restfulie and RESTEasy client frameworks. Strong coupling and hypermedia awareless As of today, Resteasy requires you to create an interface mapping every resource operation to a specific method, using @VerbName and @Path annotations to specify the desired target URI. RESTEasy is ignoring the power of [...]

Continue Reading