Hi everyone,
I’m looking for some feedback of other people’s experiences of staffing websites for long term maintenance. I’ve only ever done one off web development and then walked away from the project, so I don’t have much experience with long-term maintenance.
My current project is a University project funded by a Government grant in Australia and am required to write a costing for ongoing maintenance over a three year period, so we can secure a staff member to perform maintenance and updates.
We are expecting a minimum of 1700 students from 5 Universities to login to this site next year when it goes live, and they would be using it while they are on placement/internship which varies among institutions, but peak periods would be spread over about 20 times per year between 1st of March and 31st November.
The site uses EE, obviously and has many dynamic features although most of the processing is done client side via JQuery, so this should reduce some server load. The site is also going dedicated.
I’m thinking a staff member to look after something like this for 1 day a week would be enough to deal with any support issues and updates.
What do other people think? What other issues should I be looking at in terms of maintenance? Is 1700 concurrent logins considered a heavy load for EE, or is capable of handling much more?
Would love to hear other’s viewpoints on this.