Processes & Automation
While working on the MOOVPAD Web App and initial reverse proxy configuration, I've started to put together some clearer ideas of how I'd like the essential maintenance and monitoring processes to be coordinated across the system. These processes can be divided into two broad categories - automated and operator driven - with significant cross-overs.
What I mean by that is that although some automation will be required for all processes to some extent, all of these will eventually feed into the main MOOVPAD management system. This in-turn will link operations between the apps, microservices, and databases, as well as the RServer responsible for maintaining the underlying VM and containers.
It's important for me to get these processes and the balance between them right during the first stages. And this will be helped by the fact that the initial release phases will be relatively simple in their structure and number of components. The plan is to have the system managing these processes grow in a controlled, steady way and to gradually add more automation of routine tasks, simplifying the common operator-driven processes, so that the future team looking after all these things has an easier time keeping it all together than I've had putting it together.
Anyway... that's my morning rant done 🙂
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.