While the reservation system for COVID-19 vaccinations for 18-49 years old has been operating relatively stable, it is pointed out that the government should continue to make efforts to prevent the recurrence of the public system ‘failure’ in the future.
According to the industry on the 10th, the vaccination reservation system, which was resumed the day before, is operating without any problems compared to the operation of the system for people in their 50s.
The 18-49 years old reservation system switched the authentication system, which was pointed out as the cause of system overload, to the cloud and distributed traffic by introducing various authentication methods. Congestion levels are indicated by the color of traffic lights for each authentication method, encouraging users to select a smooth authentication method. After authentication, the system architecture was reconfigured to prevent bottlenecks from occurring during the reservation process, enabling stable service implementation through public and private cooperation.
Experts use the vaccine reservation system incident as a lesson, suggesting that efforts are required from ordering to implementation of the public system.
The system had problems from the beginning of its construction, such as unclear business order requirements.
At the heart of the reservation system are performance requirements. It is necessary to implement an accessible environment without problems even if multiple users are connected. In the project proposal request (RFP) 'Performance Requirements', the developer must satisfy ' Monitor system performance status using logs or tools (tools) during system development to identify problems in advance and take action before opening the system’ and ‘The request (search result) response time must show the initial result value within 3 seconds of the user's request.’
An industry official said, "Usually, performance requirements state that 'a certain amount of performance must be achieved when there are several simultaneous users', but there are no specific details about this." And he continued, “It is not easy for operators to identify and respond to problems in advance when the ordering party does not clarify the requirements.”
Even considering the urgency, the system construction period was remarkably short compared to the project contents.
An industry expert who analyzed RFP said, “Not only system construction, but also web vulnerability check, personal information protection, secure coding, and encryption were included in the business contents.” The export also said, “Based on this RFP, it is not appropriate business period for one company to finish this project in 2 months.”
He continued, “Even in an emergency, it is necessary to prepare a tight RFP and calculate the appropriate tasks for development within the period to implement a stable system.” He added, “This case that shows that the basics of the SW development business such as guaranteeing an appropriate business period and clarifying requirements should be well followed.”
In the future, strengthening the expertise of public orderers and building and operating a public-private cooperative network for this purpose are emerging as important tasks.
An official from a company that participated in the system improvement said, “From the system ordering stage to the handling of issues in the event of a problem, the business owner was supposed to lead the project seemed to be shifting the responsibility to the operator. For the part that is difficult to keep up with rapidly changing new technologies such as cloud, it is necessary to build a network with private companies constantly to share and grow.”
By Staff Reporter Ji-sun Kim (river@etnews.com)