Progress & Planning
The image on the left shows some further progress, with two more MOOVPAD webAPI's completed (the second still requires some minor work, to be completed later tonight), as well as the addition of two more webAPI's to the schema. These two new elements are actually just a separation of functions previously contained within other API's.
These changes are not likely to be the last, and were made to ensure both a separation of concerns and better load handling when the whole system is eventually deployed. Of course efficiency and load balancing is impossible for me to know right now, without reaching the initial testing phase. And that's where the image to the right comes in. It shows the relatively "simple" cycles for testing and deployment for me working solo. This workflow would definitely look different if there were more people working on the project, and will in future.
When I put together the release plans before, I tried to factor these testing stages into the timeline. So far, I think that any changes to that timeline (if any) will hopefully be minor. The in-house alpha testing stage will require multiple computers/systems, as opposed to the development stage. That obviously means more cost to set this up. Fingers crossed.
For now, everything is progressing (albeit slowly) towards the actual goal of having this thing done one day 🙂
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.