I'm doing an API at work where a battery system connects to some back-end that tells it what to do. for security reasons it's that way around; so the back-end is exposed and the battery system is behind a NAT'ed VPN. but it kind of reverses the roles; I'm not used to write client-server interfaces where the client connects and the server queries.
I just wonder if that's going to be super strange to the back-end implementers, and I'm not sure if I should angle the requests from the perspective of the back-end or the battery system (client).
for example, the back-end should periodically ask what the battery system's maintenance schedule is; getMaintenanceSchedule(). I think it makes sense to angle the queries from the perspective of the back-end since it is doing the requests.