- Configuration. Falcon doesn't implement it's own configuration strategy as some other frameworks do, but there are several excellent ways of handling this in your app, from using the ConfigParser module from the standard library to utilizing libraries such as those listed under Configuration on the wiki. You can maintain separate config files for dev vs. production or templatize a single file and implement a script that can render it with default values for dev/test environments. I've also seen people create their own configuration objects that simply pull values from environment variables, which can be handy when you want/need to pass options into a docker container via the environment.
- WSGI Middleware/Composition. Falcon doesn't provide out-of-the-box support for Paste, which has historically been a fairly popular way to compose WSGI applications, including middleware, for deployment. That being said, we haven't seen much (if any demand) for providing Paste support in Falcon to date. If this is something you are interested in, please let us know and we'll take another look.
Regarding reliability, Falcon has been used at scale in production by a number of companies for a couple of years now. We take care to thoroughly test the code base, and to avoid introducing (intended or unintended) breaking changes in minor point releases (ala semver). Although no software is perfect and we do get the occasional bug report, most issues submitted by the community are more functional in nature (i.e., please add this feature or tweak the functionality or interface to enable such and such use case).
Hope that helps! Let me know if you have any specific questions around these topics that I can help address.