To be quite honest, all options are going to be slower or have some thorn. SQL injection is simply too terrible of a problem to be allowed to survive. We've tried educating developers. It didn't work. More education isn't going to fix this. Yet in the meantime we've got huge problems - elections being compromised, identities being stolen, livelihoods being crushed. We, as developers, need to to take responsibility for our own code as well as those who might modify our code.
Ideally we should start seeing relational databases where injection attacks aren't possible (or at least difficult). But in the meantime there is Redis, Cassandra/DynamoDB, TitanDB, RethinkDB, and literally hundreds of other options.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
To be quite honest, all options are going to be slower or have some thorn. SQL injection is simply too terrible of a problem to be allowed to survive. We've tried educating developers. It didn't work. More education isn't going to fix this. Yet in the meantime we've got huge problems - elections being compromised, identities being stolen, livelihoods being crushed. We, as developers, need to to take responsibility for our own code as well as those who might modify our code.
Ideally we should start seeing relational databases where injection attacks aren't possible (or at least difficult). But in the meantime there is Redis, Cassandra/DynamoDB, TitanDB, RethinkDB, and literally hundreds of other options.