Function naming in backend: get/find/fetch/load

[fm3]

These verbs seem to be used fairly synonymously and randomly in the backend (e.g. find in DAOs, get in many other places. Occasionally fetch,load).

We should discuss if we want to use just one or if we want to encode specific differences (e.g. do we expect the lookup to do a linear search or is it instant? does it fetch something via HTTP/grpc? …)

[fm3]

Any opinions @frcroth @MichaelBuessemeyer ?

[MichaelBuessemeyer]

I'd go for something like that:

We should discuss if we want to use just one or if we want to encode specific differences (e.g. do we expect the lookup to do a linear search or is it instant? does it fetch something via HTTP/grpc? …)

Maybe use get if no other backend service / component ( such as core backend, data store, tracing store, redis, postgres, fossiblDB ...) is involved and fetch in case another service / component is involved 🤔