Give a promising technology room to prove its fit
Evaluate a technology with a representative workload in your own context. Establish what it can deliver, how it integrates and what operating it would require before making a wider commitment.
Give the evaluation a concrete purpose
A useful trial begins with a question your organisation needs to answer. For example, could another Kubernetes implementation support selected applications and the operating model around them?
Choose a representative workload and define the requirements that would make the result useful. This gives the evaluation a clear scope and stopping point.
Exercise the environment around the workload
Running the application is part of the assessment. Access, networking, certificates, monitoring, backup and update procedures may also determine whether the platform fits.
Where practical, the alternative can be evaluated alongside the existing implementation, using an agreed environment and representative test data.
Leave with evidence for the next decision
An evaluation can produce a record of what worked, which dependencies need adaptation and what remains untested. Operational responsibilities should be included in that account.
ModulePrime’s proposed evaluation approach combines a suitable architecture with these checks. The next step follows the findings.
Explore a technology in your own context.
Bring an option you are considering and a workload that would give it a meaningful test.