QUESTION
Would a higher Transactions Per Second (TPS) contract have prevented the February 13th issues?
1:46:16
·
60 sec
Vanessa Hunt from IBM confirms that an auto-scaling contract would have prevented the February 13th problems.
- IBM's product has a default 400 Transactions Per Second (TPS) limit.
- An auto-scaling solution would require customization.
- The current product used is an off-the-shelf option, not specifically customized for the Department of Education (DOE).
- Auto-scaling would not have encountered the same issues experienced on February 13th.
Shekar Krishnan
1:46:16
I guess let's put a question to you this way.
1:46:20
If the contract allowed for a greater TPS.
1:46:24
If there was a different TPS number contracted for a much higher one of transactions per second, rather than the 400 now that's been placed in 20 since 2018 and you're adjusting based on you know, the the the low, the frequencies, nowadays, if you had a contract with the larger amount or or auto scaling, Would we have seen the problems that we saw on February 13th?
Vanessa Hunt
1:46:49
If we had a contract with the auto scaling, no, we would not have seen those issues.
1:46:53
What they have is a custom off the shelf available product that comes with that 400 TPS ceiling.
1:47:00
So it would be that either they would go to the auto scaling solution or they would need to change behavior to be at the 400 TPS.
Shekar Krishnan
1:47:08
Got it.
1:47:08
So this wasn't some sort of customized for DOE.
1:47:11
This is an off the shelf product that deal we had.
Vanessa Hunt
1:47:13
The auto scaling solution would be customized for you.
Shekar Krishnan
1:47:16
I see.
