3 ms·

Unless I missed something there is no mention of why you want to rewrite/alter your system? - Is it for cost? - Reliability? - Scratch a tech itch? - Not fl

• themartorana 12y ago
  "Not flexible enough for future needs" is a large part of it. There are some slow-moving parts that need to be better executed, and some migration to better data stores for certain types of data, so touching a lot of the code is going to be happening anyway. Concurrency as a first-class feature would allow me to actually simplify things, which is a bonus, as I am loathe to use the threading or multi-processing libraries in Python. I could rewrite parts in say, Twisted, but that's still rewriting. This is not scratch-a-tech-itch, I assure you. I have plenty of new work to be done that will give me that. It's about taking an academic exercise and battle-hardening it and making appropriate design decisions for scale even above where we currently are. (Squeezing more req/s out of each AWS instance isn't going to hurt our bottom line either, but that's secondary.)