“sorry, our database cannot be exposed to the public network, we can provide API for the app, you can give us what data you want and we will provide you an data APIs and authorization API to get token.”
Does that mean I can use Glide’s API to access the required data?
I’ve used the API to access data before (passing a car rego to a public database and retrieving more info about the car). In this case I’m wanting to get similar info about fleet cars from an internal database, but more comprehensive, information about servicing and tyre changes etc including due dates. This data would then be displayed in the app.
Is the Glide API the right option for accessing this data?
I think the answer depends on how the data will be used. I mean, is it intended that the SQL Data is the master for the Glide App, and you somehow want to keep the two synchronised?
I’ve been down this path before and we ended up with a two-way sync, depending on the type of data. We split it into two broad categories as follows:
Configuration Data: Data that rarely changes, that is used to drive business logic. The Client SQL Database is the authoritative source of this data. Tables are mirrored in the Glide App, and changes are pushed from the clients system to Glide via the API.
Transactional Data: Data that is collected in the App, and is constantly being added and edited. Glide is the authoritative source of this data. The tables are mirrored in the clients SQL database, and changes are pushed from Glide via an API that the client provided.
So again, the answer depends. You might end up using the Client provided API, the Glide API, or some combination of both.