All Glossary

Digitalfire API

Insight-live.com cloud servers hold a lot of subscriber data, almost all of it confidential. Traditionally our webapp reads and writes directly to the database through functions designed to abstract it. In recent years almost all companies have been moving to an API model, with two teams of programmers. One organizes and secures the data on a cloud server, this is called the "back end". Another team works on web and mobile apps that make calls to that data, they focus on the user experience (called the "front end"). These two teams can be on different continents and have their own cloud computing infrastructures. This approach forces the organization of data, security measures and standardization of the syntax to request and receive the data. APIs expose a CRUD interface (with create, read, update and delete methods). The data source can cache data and meter and measure consumption of each account. Anyone subscribing to the data source can theoretically create an app that queries and updates data.

Starting in 2022 we began work on exposing Insight-live data in an API. We have security mechanisms in place now and it is operational for subsets of the database schema. When ready we will convert the Insight-Live webapp to use it, this will vastly simplify it by removing all the database code. After proving the method we will expose the API for subscription to anyone wanting to write an app. The end result will be new apps with new functionality.

At the same time, we are also writing APIs for the data at the Digitalfire Reference Library, at PlainsmanClays.com and at RonGetty.com. All of these, including shared records at Insight-Live.com, will feed the code that creates the library.

Related Information

Links

By Tony Hansen Follow me on

Got a Question?

Buy me a coffee and we can talk