Get the basics right. Your code will consume memory, CPU, and I/O. Use asynchronous I/O to minimise time spend by your code waiting on I/O for data to process. Be wary of forcing your code to serialise access to a resource (e.g. a database table row, record in a file, a shared memory segment, etc). 

And INSTRUMENT your code so that you know exactly what your code does, WHERE, WHEN, and FOR HOW LONG. Without code instrumentation you will be in the dark as to what portions of your code perform and scale well, and which portions don't.
spam fails_task lang_mismatch pii not_appropriate hate_speech sexual_content quality toxicity humor helpfulness creativity violence