"The way we store student coding activity is in a table that until today had a 32-bit index... The database table could only store 4 billion rows of coding activity information
if it can only store four billion rows, it isnt "the cloud." its just a KVM instance running on a shared hosting facility then, isnt it.
we didn't realize we were running up to the limit, and the table got full.
so not only were you incapable of scaling your infrastructure or your program to handle four billion rows --something every sysadmin on the planet is capable of-- you weren't even competent enough to set up monitoring for it.
We have now made a new student activity table that is storing progress by students.
the ones that lost all their data dont care. the students will leave to try something else, the educators will fall back on lesson plans that werent written by a corporate think tank, and your 'hour of code' will remain just another hour of minecraft in a kids life.
With the new table, we are switching to a 64-bit index which will hold up to 18 quintillion rows of information.
you dont get it. no one fucking cares about your SQL table limits but you, and youre oblivious to the fact that a table with eighteen quintillion rows would never load. code.org will be no different than the spanish or french class in a kids life. a fractional percentage of them will actually go on to use it as a career.