It's an electronic testing and examination environment for German universities.
It's very far from big data, but we have to support very small universities with very limited tech budget. We pre-generate and store the exams to ensure that we do not have any compatibility issues in the future (e.g. by changing minute elements of the randomisation).
The biggest database currently is about 700GB and I assume that we'll reach an equilibrium at around 2 TB.
I chose markdown for a large project due to the reduce storage size and forced simplicity and abstraction.
I have to work with static data which will not change for 10 years, the only way to keep it alive is upcasting the internal structure and updating the conversion to html.
The project lives in a scientific environment but is used by a wide variety of people.
The project is now 5 years old and until next week there was no wysiwyg-editor (I'm currently working on it).
It's very far from big data, but we have to support very small universities with very limited tech budget. We pre-generate and store the exams to ensure that we do not have any compatibility issues in the future (e.g. by changing minute elements of the randomisation).
The biggest database currently is about 700GB and I assume that we'll reach an equilibrium at around 2 TB.