The next logical chunk of functionality to attack in hms_sys is the Artisan Gateway Service. This service waits for input from either Artisan or Central Office end users, creating or updating object data as needed, and perhaps synchronizing that data with the web store system's database. Both of the end user applications are expected to communicate with the Artisan Gateway Service on a completely random basis; whenever someone wants to make a change to the data, it'll be ready and waiting to process that request.
Before we can really implement this service, however, we need to work out how any service can or should work, written in Python. To that end, we will have to examine and understand the following:
- The basic implementation of the structure of a service, including the following:
- Options for managing the configuration of a service...