Re:How NoSQL forced the evolution of a scalable relational d...
by mpweiher on Friday July 13, 2018 @04:39AM
(#17521390)
> kicking out as many layers between a relational db and a REST Api
Cool, is there anything we can see? I pretty much stumbled upon something along those lines back in 2003, and developed it into what I now call "In-Process REST"[1][2] and "Polymorphic Identifiers"[3][4].
The idea being that you can stay within a "storage-oriented vocabulary" for as much as possible, and that can include seamlessly all the way from provided interface to various storage mechanisms.
What's neat is that it reduces friction a lot, greatly enhances composability and reusability and just makes things blatantly obvious.
Cool, is there anything we can see? I pretty much stumbled upon something along those lines back in 2003, and developed it into what I now call "In-Process REST"[1][2] and "Polymorphic Identifiers"[3][4].
The idea being that you can stay within a "storage-oriented vocabulary" for as much as possible, and that can include seamlessly all the way from provided interface to various storage mechanisms.
What's neat is that it reduces friction a lot, greatly enhances composability and reusability and just makes things blatantly obvious.
[1] https://link.springer.com/chapter/10.1007/978-1-4614-9299-3_...
[2] https://github.com/mpw/SoftArchLon2016-In-Process-REST/blob/...
[3] https://www.hpi.uni-potsdam.de/hirschfeld/publications/media...
[4] http://objective.st/URIs/