[EXT] A general question about the downsides or gotchas of rlm_rest.

[Brian Julin]

work vlpl <thework.vlpl at gmail.com> Wrote:
> So, I want to ask: does rlm_rest have any downsides compared to rlm_python3? Maybe something not obvious or critical that I should consider before deciding to use it?

In one application we tried but could not use rlm_rest because it built too many connections... one per server thread.   That's great for contention-free operation but not so great if the target device has limited connection capacity.  Instead we pushed changes to a local database with rlm_sql and had a separate process read it off the back end of the database to feed it to the target device over a single connection.  The database core took care of preserving consistency through its transaction mechanism.

We found rlm_sql to be great for this purpose as it can be configured to quickly fail without any delay when the database connection goes down, so if you are doing something that does not need to impact the immediate response to the request and just handles followup activities, I'd look into that.