Broad Strategy Overview
As an Australian tech business, one of the major disadvantages can be remoteness. This can of course be overcome by remote deployment strategies, but this in turn has its own set of challenges. And so I'd like to briefly consider some of the considerations regarding hosting of the MOOVPAD Web Apps and webAPIs.
In the immediate term, initial testing will combine local in-house and cloud deployment for various parts of the projects. Short-term (12 month) goals involve having a larger portion of the deployment being cloud based. Medium term (24-36 month) goals will see a greater focus on shifting towards some local datacenter co-location. This allows MOOVPAD servers to be custom built and the hosting supported by local infrastructure where possible. And the eventual goal is to gradually transition towards local in-house hosting (long term).
Given MOOVPAD Web Apps will be developed as progressive web apps (PWAs), the main challenge will be after the apps are downloaded to the users' client devices (i.e. transfer speeds of composite data, rather than app UI). This can then be managed using distributed cache and event-driven architecture approaches.
Yeah I know... let's pretend I understand what I just said 🙂
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.