pingf
How does it compare to Connexion?
I just discovered your project today and would be interested in how it compares to our Connexion API-First Framework. I'm one of the maintainers of Connexion.
actually it is a project inspired by the connexion framework and serveral other frameworks. so you may find these two frameworks looks very familiar excepts:
-
falsy is my own interest side project, while connection is much bigger and well maintained. even though we have serveral small project based on falsy running in prodocution, I have to say that it's less maintained right now. Cause we are a very small company, we do not have a production team. I have to put more effort in the line of bussiness(which makes me very sad), I hope I may have some time to refactor falsy and add new features to it.
-
falsy is based on falcon while connection is based on flask. It seems flask is the only backend of connection. the backend of falsy is falcon right now, however, I have start another project making it works with aiohttp(which is blocked right now due to the problem of not having enough time)
-
falsy is in a part of my own big "toy" plan(which also have serveral other projects: netboy(the crawler supports pycurl and selenium), store(the json storage framework), store_beat(celery dynamic beater for store)). I have found zalando seems have similar plan, like the crawler zalenium (which is written in Java). my tools are all written in Python, and I will create another project built upon these tools in the feature. I'm not sure whether Connexion is part of the "plan"
-
falsy lacks the features of testing and the validation is via the validationId, however, connexion supports these better. falsy has other "Ids" like 'beforeId' and 'afterId' for aop hooks. falsy supports multi versions of swagger-ui. falsy supports the include of sub yaml files.
@pingf thanks for the elaborate answer! :smile: Just FYI: Connexion now also supports aiohttp and I tried to implement Falcon support, but I dropped it as it was not worth the effort (Falcon is more lightweight, but Flask allows more integrations and the performance difference is not so big).