Open APIs

Hello,

I am trying to implement Resource activation (RA) for activating a resource. But our vendor system has no throttle mechanism. In RA, we are need to organize throttling for the system. If RA has throttle mechanism. It should be splitted to 2 programs. First one receives resource request and insert it to a queue. Next one fulfills the resource activation. I don't know if RA functions should be splitted. What options did you implement?

Hi Myagaa

I don't know very much about the details of resource activation. But specifically for throttling, simply writing the request to a queue won't help, since I'm guessing that your vendor system won't be able to take the request directly from a queue. You'll have to write some software (or see if you can find equivalent on the Internet) that you can trust, which does the throttling. For example if you want to control the throughput to (say) one request every 10th of second (0.1s), you'd have a wait timer in your code that goes off every 0.1s and retrieves the next message from your topic.

You'll also need to manage failures (such as if your vendor system couldn't honor a particular request), perhaps by writing failed requests to a Dead Letter Queue (DLQ), and then having human or automatic handling of the failures.

Good luck

Hello,

I am trying to implement Resource activation (RA) for activating a resource. But our vendor system has no throttle mechanism. In RA, we are need to organize throttling for the system. If RA has throttle mechanism. It should be splitted to 2 programs. First one receives resource request and insert it to a queue. Next one fulfills the resource activation. I don't know if RA functions should be splitted. What options did you implement?

Hi Jonathan,

Yes, the vendor system can't get data from the queue. RA receives a "resource" request, it stores the request as what it receives on the queue. If it stores the request successfully on the queue, it just respond acknowledge the request to what a client call it (Resource order management). Another application throttles reading the queue. When it reads "resource" data from the queue, it transfers a request to vendor system's api. In order to implement the throttle, RA should be splitted to the 2 different programs. My question is how good solution it is.

Hi Myagaa

I don't know very much about the details of resource activation. But specifically for throttling, simply writing the request to a queue won't help, since I'm guessing that your vendor system won't be able to take the request directly from a queue. You'll have to write some software (or see if you can find equivalent on the Internet) that you can trust, which does the throttling. For example if you want to control the throughput to (say) one request every 10th of second (0.1s), you'd have a wait timer in your code that goes off every 0.1s and retrieves the next message from your topic.

You'll also need to manage failures (such as if your vendor system couldn't honor a particular request), perhaps by writing failed requests to a Dead Letter Queue (DLQ), and then having human or automatic handling of the failures.

Good luck

Hello,

I am trying to implement Resource activation (RA) for activating a resource. But our vendor system has no throttle mechanism. In RA, we are need to organize throttling for the system. If RA has throttle mechanism. It should be splitted to 2 programs. First one receives resource request and insert it to a queue. Next one fulfills the resource activation. I don't know if RA functions should be splitted. What options did you implement?

Hi Jonathan,

Yes, the vendor system can't get data from the queue. RA receives a "resource" request, it stores the request as what it receives on the queue. If it stores the request successfully on the queue, it just respond acknowledge the request to what a client call it (Resource order management). Another application throttles reading the queue. When it reads "resource" data from the queue, it transfers a request to vendor system's api. In order to implement the throttle, RA should be splitted to the 2 different programs. My question is how good solution it is.

------------------------------
Myagaa Nm
Mobicom Corporation

Original Message:
Sent: Feb 29, 2024 03:25
From: Jonathan Goldberg
Subject: Resource activation throttling

Hi Myagaa

I don't know very much about the details of resource activation. But specifically for throttling, simply writing the request to a queue won't help, since I'm guessing that your vendor system won't be able to take the request directly from a queue. You'll have to write some software (or see if you can find equivalent on the Internet) that you can trust, which does the throttling. For example if you want to control the throughput to (say) one request every 10th of second (0.1s), you'd have a wait timer in your code that goes off every 0.1s and retrieves the next message from your topic.

You'll also need to manage failures (such as if your vendor system couldn't honor a particular request), perhaps by writing failed requests to a Dead Letter Queue (DLQ), and then having human or automatic handling of the failures.

Good luck

------------------------------
Jonathan Goldberg
Amdocs Management Limited
Any opinions and statements made by me on this forum are purely personal, and do not necessarily reflect the position of the TM Forum or my employer.

Original Message:
Sent: Feb 29, 2024 01:58
From: Myagaa Nm
Subject: Resource activation throttling

Hello,

I am trying to implement Resource activation (RA) for activating a resource. But our vendor system has no throttle mechanism. In RA, we are need to organize throttling for the system. If RA has throttle mechanism. It should be splitted to 2 programs. First one receives resource request and insert it to a queue. Next one fulfills the resource activation. I don't know if RA functions should be splitted. What options did you implement?

------------------------------
Myagaa Nm
Mobicom Corporation
------------------------------