Forum Discussion
CirrusAS3 Best Practice
CirrostratusShripatymay I ask you how this case continues? We send extensive amount of API calls to our F5s, but they're all Rest API calls (imperative), and that probably does not cost so much CPU as the declarative API the AS3 uses. We're forced to switch to AS3 due to NEXT OS slowly approaching, but I wonder about the consequences and "lots of errors" is something I don't experience now with Rest API and definitely don't want to with AS3. Thank you
AdminHi Zdenek Just to be clear, BIG-IP Next will not have the same control plane challenges with API calls that exist with classic BIG-IP.
The issue at scale with both AS3 (which is an iControl LX package) and iControl REST is the shared restjavad process, so a lot of calls with heavy payloads will be impactful either way and need to be managed accordingly. If you aren't having issues today, I don't anticipate that will change with your shift to AS3, but testing in a lab on large configs will be helpful to determine that in your environment.
