Mike Amundsen
|
As API Architect at CA / Layer 7 Technologies, Mike Amundsen is Director of API Architecture and part of CA's API Academy. He is responsible for working with companies to provide insight into how best to capitalize on the myriad opportunities APIs present to both consumers and the enterprise. |
|
Source Code for my ToDo Server that supports both Cj and HAL+JSON is here
| Title | Is there a sufficiently stable definition of REST? |
|---|---|
| Level | Five-In-Five |
| Abstract |
This question was posed on the APPS-DISCUSS list recently. I think it's a good question. While some would simply answer "No", I think we can do better. REST is a style, not a spec but I think it can still be defined sufficiently. And a stable definition could go a long way toward helping everyone understand each other just a bit better. I think a useful definition will incorporate bits of Fielding's dissertation plus some of his commentary and blog postings, all within a framework similar to that used to define other styles such as "Impressionism", "Swedish Modern", and "Gothic." Let's see if we can come up with something useful at RESTFest! |
| Supplemental |
|
| Slides |
| Title | Creating the APIs of the Future |
|---|---|
| Level | Extended Talk |
| Abstract | Change in inevitable. If your API will last a long time you need to handle change. APIs that can't handle change - that are static - are basically "dead." This talk covers suggestions on how you can handle changes over time using designs for messages on the wire as well as patterns for code on both the client and the server. |
| Supplemental |
|
| Slides | Slides |