It (nix) kind of hung around in the background with the team that used haskell for awhile, but became prime time when we needed to support a range of VMs running within client infrastructure that were in reality just running various python scripts under supervisord (). I convinced (previous) $dayjob to use it. HTTP clients often use a default timeout value for requests, and it's a best practice to use such a timeout - so you'll need to coach your partners consuming this API not to use timeouts for your API. Consider that if an app server serving web site traffic is waiting for a slow request to your API, then both app servers are affected - you're now holding resources on the web site and the API, effectively. That may be fine with a small number of consumers, but if you point your web site at this API, you may run into problems. The problem with slow requests is that they tie up app server processes and usually also database connections.
Rqscheduler password#
Make sure your redis instance has a password - redis 6 supports ACLs as well You can add rq-scheduler for that though: Did you mean RQ (redis-queue)/django-rq? If so, it works well as long as you don't need a scheduler for cron-like tasks, which it doesn't include.
Storing API keys in Redis with AOF and RDB persistence turned on is going to be way faster than storing those keys in Mongo.
0 kommentar(er)
