How The Pieces Fit Together
With all of the work on the WebAPIs and different server-side components, I thought it would help to get an overview of what the pieces do and how they integrate into a cohesive structure. The main screenshot below is a simplified look at these different elements.Underlying all of the instances of the MOOVPAD Web App and webAPIs are the MOOVPAD Management System and MServer pipeline, gathering and delivering important information across the system.
These link together the different, distributed instances of the web app and webAPIs with their associated databases, seen clustered together with the RServer and BServer nodes. These latter components will be responsible for managing things at the OS-level of the VMs, while the MServer nodes within the containers will be handling the interaction with the web app /API elements and reporting back to the MOOVPAD management system.
All to make the pretty lights on the screen go beep boop 🙂
Stay awesome,
EMH
HOW MOOVPAD IS BEING BUILT
For the overview of how MOOVPAD apps are being developed, the reasoning behind particular decisions during development, policies, and more in relation to all the technical things, please see the link to the left.
This will be an ongoing work in progress, and will always be linked to the bottom of each upcoming Blog post.