What was the Problem / Challenge trying to solve for?

SEAS was using a legacy system which had several limitations that needed to be addressed.

  • The old system required multiple database instances which increased environmental expenses. Old system was hosted in RackSpace on physical machines.
  • Need to be scalable in order to on-board new school districts and states rapidly.
  • Need to scale down during off-peak times of the year (e.g. summer break, winter break, spring break).
  • California mandated a paper-reduction initiative.
  • Legacy system was unable to report on all fields within the application. Database tables/fields differed between school districts and states which created a …

What did Metova do to solve that problem?

The new system was able to:

  • Use AWS VMs in order to reduce monthly environment expenses by ~50% cost savings going to AWS. The new application was built to be multi-tenant and a SaaS model allowing for multiple districts to be hosted within a single database instance.
  • All fields stored in the AWS database is reportable.
  • Scalable to stand up new School districts or states as needed. Site set up could be scripted and run on predefined schedules. Introduced the ability to spin up additional sites for training and demos as needed.
  • AWS allowed for scheduled events (e.g. reduce front-end resources over long weekends, holidays, breaks, or scale up during peak times of the year).
  • The new application allowed for a more flexible UX & process flow, collapsing older forms into fewer pages for teachers to fill out.

What technologies were used along with AWS?

  • AWS – uses EC2 & RDS for scalability and cost management
  • Security for HIPAA / FERPA compliance enforced within the multi-tenant structure and restricting end users from accessing the actual AWS environment. User roles and permissions are defined by admins and prevented from viewing sensitive information while access to the db is restricted to approved SEAS personnel.

SEAS homepage: