abalashov left a comment (kamailio/kamailio#4603)
I would start by acknowledging the incredible amount of work @miconda does to
keep the project together, and that this is open-source, so beggars can’t be
choosers. Having said that, I would tend to agree with @rennykoshy here.
The DB comparison is limited because DBs are typically (though not always) in
the critical path of call processing. The argument about DBs has always been:
“if your DB is down, you’ve got bigger problems”. This is probably true in
almost every scenario, although, as @rennykoshy points out, there are ways to
architect Kamailio so that a slow or overloaded DB is more or less of a
catastrophe.
EVAPI can be in the critical path too, if using `evapi_async_relay()`, which I
use heavily. However, it started out as a module that can emit events to
passive observers. If one of those observers blocks or is slow to read the
events for whatever reason, it shouldn’t take request processing down, IMHO —
if it were up to me. :-)
@miconda makes a good point that there are other Kamailio constructs that can
be used to layer more async queueing depth internally. I actually forgot that
`$mq_size()` exists — I don’t think it’s always existed — so that it’s possible
to do discards via an internal asynchronous pipeline. That may be the way to go
here for @rennykoshy’s use-case.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/4603#issuecomment-3965950092
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/4603/[email protected]>
_______________________________________________
Kamailio - Development Mailing List -- [email protected]
To unsubscribe send an email to [email protected]
Important: keep the mailing list in the recipients, do not reply only to the
sender!
