It's a given that most programs and systems have a need to store and retrieve data to operate with. The alternative, embedding data into the code itself, is simply not practical, after all. The specific shape of the data storage involved can vary wildly, based on the underlying storage mechanism, the specific needs of an application or service, and even on nominally non-technical constraints such as the need to not require end users to install other software, but the fundamental need remains the same, no matter what those factors add up to.
The various component projects/sub-systems of hms_sys are no exception to this:
- The Artisan Application will need to allow Artisan users to manage the products that the Artisan is creating and selling, and to manage at least some of their own business entity data
- The Artisan...