oduwsdl
Consider using Responder instead of Flask
In #613 recollected that we were considering moving to Responder from Flask.
Would there be advantages and/or ramifications of doing so? Let's document them here to see if it would be worthwhile.
Flask is a well-known and battle tested framework which has been around for many years.
Responder is pretty new and modern framework which has better testing integration using a very well-known and popular library called Requests. It has some other modern features such as built-in support for GraphQL, interactive API documentation using OpenAPI Schema, background tasks, and class-based REST-style views.
Moving to Responder will require some work, primarily in how routing and exceptions are handled. Also, I am not sure how well it supports RegExp-based routes which we would prefer to use in some places.
Great information, thanks for this review, @ibnesayeed. While we resolve the outdated Flask issue in #616, we might look to Responder for the reason of the built-in support (namely GraphQL, which we've discussed in-person) you mentioned above.