Thank you all for the replies.
Our team is currently developing a rule-based modeling system with all the necessary scripted national building regulations of the city we chose. The aim of this project is to allow developers to get a quick idea of the lot from our volumetric study. Thanks to Rhino API, we have successfully managed to build the system working for our trial zone in Rhino 6.
Since we have planned to distribute this service as a web service, we were looking for the 3D modeling engine such as Rhino Compute and Blender, which allows geometry computing in a cloud environment with Rhino API. Whenever developers click the site of their interest, we plan to offer various 3D massing analysis instantly upon the request.
There were two options which we initially considered if we use Rhino as a modeling engine at the back-end.
First, we can install Rhino in a local environment and receive the request directly from users. This option carries lots of shortcomings - A server computer with Rhino software must be ON all the times and parallel computing is not possible unless we purchase multiple licenses. Therefore, our engineer said this would carry too many risks for our web service.
Secondly, it is Rhino Compute. It seems that only one instance of Compute per VM is currently allowed. My understanding of Rhino Compute might be wrong, as I just started to look at it. It seems that every Geometry operation calls for Rest API.
In our prototype system, the process at each modeling stage employs more than 100 Rhino APIs. I guess, then, the system needs to call Rest API every time whenever the script uses Rhino operation in one modeling process. This is our main concern with the current Rhino Compute, if my understanding of Compute is correct.
It will be much appreciated if you can give us some advice/recommendation regarding this matter.
Look forward to hearing from you soon.