Earlier I've posted this question (link) on Programmers Stack. Why was it closed and what can I do for it to be reopenned? Note: I've already made some edits taking in account the argumentation provided by the closers.
The original version of your question was very broad, and read more like a thesis than an actual question. It seemed like you've already made your mind on almost everything you were asking about, and if that's the case, why ask?
To make matters worse, your question is of the "foo vs bar" variety, and strictly speaking those are off topic:
and it is not about...
- what language/technology you should learn next, including which technology is better,
Broad comparisons don't really work, we all have our favourites. If you don't give us enough parameters to make a sane comparison, the question is in danger of turning into yet another flame war. And yours almost did, the back and forth in the comments was getting out of hand. No one is to blame here, we all got caught up in the conversation.
Your edit was a step in the right direction, you removed your conclusions from the question, and it certainly reads more like a question now than a thesis. But you really need to do another update, and give us a few more details on the actual design.
With almost each one of your clarifying comments you revealed design idiosyncrasies, the project seems to have a very unique design. Every detail about it will help the community give you an actual answer, and not just opinions and speculation. You said in a comment that if you give us more details, the question would become "too localized". That's certainly a risk, but "too localized" is far better than "too broad/possibly flame-ish".
What I'd like to see in your question is:
- A very brief and very high level overview of OTServs design. Why, for example, is a crash so devastating, why isn't there any redundancy?
- A high level overview of the database schema, not just the table names. You mentioned in a comment that items don't have unique IDs, add that to the question.
- A brief outline of usage and traffic. Solutions for 500 concurrent users will be quite different from solutions for 5*10^6 concurrent users. Be precise and avoid words like "huge". A one million rows table is "huge" only if you haven't worked with billion rows tables.
- A somewhat detailed outline of what you need to save and when.
- Tell us what's beyond your control, what you can't possibly change.
All in all, it's a good question, but you've approached it from the wrong angle. Tell us what the problem is, and we'll do our best to help you solve it. But if you've already decided on a solution, then post it on your blog, not here.