I tried to push things to the max so was refering to licence tier 4.
I would have seen a licence tier 5 for unlimited API calls

Hello Cloudbeans,

We are happy to hear that you are trying the boundaries of the application.
Can you please provide us with your review of the application and its features?

Which boundaries are we talking about? Did you make 1M API calls and 150 rules already? :O

Regards,
Erik

Hi,

> Which boundaries are we talking about? Did you make 1M API calls and 150 rules already?

Certainly not as i don't yet even master decisionrules.
I point just one point : when you do automated trading, this means you will make quite a few API calls to the trading platform.

In my case, i'm not to the point of doing high frequency trading. On sport trading i do a call to the platform around every 30 seconds.
In one month, that represent (31 * 24 * 60 * 60) / 30 = 89 280 API calls.

In sport trading you have around 5 betting exchange platforms in the world which we can consider as serious.
We also have 4 aggregators platform of betting exchanges market & Bookmakers market so as a total of estimated API calls we have : (5 + 4) * 89 280 = 803 520.

I don't know what is an API call for decisionrules but if in the inner process logic, making a call to a rule flow can imply to be interpreted as several calls then we are already above the million.

If i trade crypto and/or stock market, i'm already above the million as well.

Also note that in my trading example i considered one call made to the trading platform would imply to do only 1 call to decisionrules in the software which is not realistic so the 1M is very quicly reached.

Hello,

API call = decision, evaluation of the input based on the conditions.

As Prabhat mentioned in the previous comment it depends on the data model, the execution strategy, and if you make simple calls or bulk.

Bulk means, 1 API CALL (decision) with multiple inputs, for example, your 86k inputs can be only 1. Please see the documentation https://docs.decisionrules.io/doc/api/rule-solver-api

Obviously, it depends on the nature of the rules, data model, and other variables. We would be interested in scheduling a call with you to understand your use case and to answer the questions you might have.

I want to point out the fact that the AppSumo deal is not suitable for corporations making 100 million decisions in a month, because of the different requirements on the SLA, uptime, deployment model,...

Thank you.
Erik

Hello,

>Obviously, it depends on the nature of the rules, data model, and other variables. We >would be interested in scheduling a call with you to understand your use case and to > >answer the questions you might have.

Thanks. My use case is basic, really, it's just around trading stuff, no big mysteries in there.
I'm just on the fence between tier 4 and play with it for a while but i wonder about this api call limitation and also uptime which is critical, reason why i was more insterested into the premise option but as you mentionned, not possible in an appsumo deal.

>I want to point out the fact that the AppSumo deal is not suitable for corporations making >100 million decisions in a month, because of the different requirements on the SLA, >uptime, deployment model,...

Based on what i was saying up to suggest a tier 5 with unlimited api calls, it was just to cover my scenario for which we were around 1 million API calls and if i maximize estimations on crypto exchanges platforms, i would say more or less 10 platforms could be covered so around 1 M more API calls and the same for stock market brokers.

So in total, if i would have to give a number, instead of 1M, i'm looking for 3M based on the consideration i would do only 1 api decisionrules call after i get result from the api call made on the trading platform. In reality, i think i would have to do 2 or 3 api calls instead of this one, so that would multiply the 3M up to 9M.

I don't know at this level if all of this could be encapsulated in one rule flow and if that can be considered as one API call. If yes, then i would be possibily back to a 3M API call need.

Hello,

I understand your standpoint and the concern about the number of API calls. Unfortunately, in this deal, we can't incorporate unlimited API calls for a lifetime.

If you create a rule flow with 20 rules and you execute it, it is considered as 1 API call.

Regards,
Erik

I like your humor ;)

We would appreciate your feedback on the DecisionRules. You have done a lot of research and work on your side to try the tool out.

Thank you.
Regards,
Erik