> You're missing the point. Obviously, you can write your application in Cython and have decent performance. "Decent" is a weasel word, which suggests that the

> You're missing the point. Obviously, you can write your application in Cython and have decent performance. "Decent" is a weasel word, which suggests that the performance hit of following this approach is tolerable or acceptable. Sometimes it is, sometimes it isn't. It really depends on where you place the glue code, and where you expect the hot path to be. In the case of a self-described "Redis clone" which ends up being Redis itself glued back together with Python, I'm not sure you can make that case. > The entire purpose is to demonstrate that you can build a reasonable performance application built on high performance libraries and stick with idiomatic Python code. I'm sorry to say but that isn't much of a demonstration. I mean, Python is already widely used as glue code to hold together high performance libraries, and it's already widely known and understood that gluing together code with Python brings in a significant performance hit. And that's ok, because people do it as a tradeoff between performance and some other kind of value-added. But in this case I fail to see what value-added is being proposed, other than the personal portfolio side of things.