Relational state transfer: Difference between revisions
no edit summary
No edit summary |
No edit summary |
||
| Line 5: | Line 5: | ||
"Like REST's requirement to keep state accessible to all possible participating entities in a session, relational databases require that transactions be permanent, and that once committed, the changes stick." | "Like REST's requirement to keep state accessible to all possible participating entities in a session, relational databases require that transactions be permanent, and that once committed, the changes stick." | ||
"The main differences would appear to be the complexity of the arbitrary [[semi-structured data]] that is assumed to be manipulated by [[REST]], the availability of redundant sources (unlike an RDB which explicitly requires each item to be authoritatively in one place in one table), and the necessity of arbitrarily-complex resolution of which data to trust, which is assumed to be a human problem in REST but in relational databases, is more or less assumed to be up to the programs." | |||