A preface: as it usually happens with my favorite topic, neither database conferences, nor software engineering conference acknowledge that kind of research. Thereby, when although the paper got accepted, it was accepted as a short paper (because nobody understood what it was about :)).
Moreover, two days before the conference we were asked to shorten the presentation to 15 minutes. Fortunately for me, there was one no-show at our session, so I was able to present in full. Below is a full presentation version including two slides which were not in today’s presentation.
NORM – SOFSEM2020
Filed under events, talks
I’ve been thinking for a while how to name our methodology of data exchange between databases and applications. Several years ago, we came up with the term HDAT – Holistic Database Application Tuning.
This term didn’t get much recognition, partially because I didn’t really like it myself. It is pretty vague and implies that the subject we are talking about is something “nice to have” rather than entirely new technology.
In an attempts to highlight the most important feature of this technology – the fact that it eliminates a need in any ORM – I came up with the term which I am going to introduce today: NoRM.
The letter ‘o’ stands for both ‘No‘ and ORM, to avoid double ‘o’ and any possible associations with “Noom”:). Also, it highlights the fact that this approach is natural, that this is “a new norm.”
From now on, I am going to call “this JSON thing” a NoRM approach or NoRM technology.
How do you feel about it? Do you like this term? Will you use it?