4 ms·
Eh, 'service' is an extremely overloaded term, so constructions like 'HTTP service' and 'JSON service' are ambiguous and awkward. I actually rather prefer the t
by niftich 10y ago
Eh, 'service' is an extremely overloaded term, so constructions like 'HTTP service' and 'JSON service' are ambiguous and awkward. I actually rather prefer the term 'API' used as a metonym [1] to describe the running instantiation of the 'actual' API, because the meaning is disambiguated by context.
[1] https://en.wikipedia.org/wiki/Metonymy https://en.wikipedia.org/wiki/Metonymy
- allthingsapi 10y agoWe tend to use the term Web APIs to capture the space - we should have used that in the title to keep the discussion focused on the Monitoring topic!
- dozzie 10y ago> [...] because the meaning is disambiguated by context. Until it's not disambiguated, especially that API and service implementing the API are in quite close domains and they will cause trouble in understanding. Really, no need to pollute our already difficult jargon with "API" meaning "service" ("API service", if you feel that "service" is overloaded).