Why we build it
In order to enable the appropriate device configuration options, SightStream needs a service to determine which devices and capabilities triPOS supports.
How we built it
The Devices API was built using an Azure Functions back-end with API Management acting as a front-end for the back-end. The Azure Functions and API management configurations are in Azure's git version control with deployment happening every time an update is pushed.
What's next for the Device Capabilities API
- Add additional supported devices.
- Move this into a local TFS git repository.
- Create a method for deploying/testing in QA and PROD.
- Create permanent API Management instances for the necessary environments.
Log in or sign up for Devpost to join the conversation.