Date: February 20, 2025
Update: Looking at the Google cloud compute numbers so far, we’ve decided that we have to switch [back] to AWS servers. Not only are there fundamental issues with Google cloud when it comes to how it’s computed, but for indema’s growth we think it is critical for the change back to something more stable. Further, AWS has been in the cloud computing space longer, leading to a more extensive and diverse portfolio of services. This is particularly appealing to us with complex or specialized needs.
Further, AWS has a very large and mature ecosystem. This means that many third party tools (ones that indema depends on for integrations such as QBO, XERO and more), is already designed to work with AWS.
Process:
Migrations started [DONE]>
Forward to security team to implement security [DONE] >
live server testing [DONE as of 2/5/2025]
Impact on development: The only impact this has on development would be the time it takes for our lead developer to set up the new instance with AWS (roughly 1 day).
Date: February 25, 2025
Update: Migration to the new AWS system is fully complete and stable as we monitored it the past few days. We are finalizing some details on the front-end UI, with me actually dipping my toes in development to help the team out a bit. Back-end had some setbacks during migration for 2 modules that our lead developer is taking care of but does not impact deliverability with indema 4, nor performance.
Some good news: we have a live server where I can login to an account. One step closer to launching, but of course have to get to that 99%. Not shooing for 100, but close to it.
Process: Nothing to report.
Impact on development: Nothing to report.
Date: March 1, 2025
Update: We added a few of our beta testers to the system to test the already completed modules. Testing updates from that team are expected every week, with those improvements happening to the provided feedback shortly after. Fine-tuning how this is done on our side, but are confident that we can just focus the following week on those pieces of feedback, while the other half of the dev team focuses on the other modules currently in progress.
Process: Nothing to report.
Impact on development: Nothing to report.