Trivial REST:
(1) Declare a case class
(2) Register it as a Resource, specifying the allowed HTTP methods
(3) You get a truly RESTful API, your allowed HTTP methods, and persistence, and caching, for free.
Trivial REST:
(1) Declare a case class
(2) Register it as a Resource, specifying the allowed HTTP methods
(3) You get a truly RESTful API, your allowed HTTP methods, and persistence, and caching, for free.
(4) -- and a few days later -- when you need to migrate data, simply declare the migration rules
Concepts to explore:
Case classes as a schema for JSON
Postel's Law / The Robustness Principle - http://en.wikipedia.org/wiki/Robustness_principle
Multiple versions of a case class supported at the same time
Trivial REST: (1) Declare a case class (2) Register it as a Resource, specifying the allowed HTTP methods (3) You get a truly RESTful API, your allowed HTTP methods, and persistence, and caching, for free. (4) -- and a few days later -- when you need to migrate data, simply declare the migration rules
Concepts to explore: Case classes as a schema for JSON Postel's Law / The Robustness Principle - http://en.wikipedia.org/wiki/Robustness_principle Multiple versions of a case class supported at the same time