Eric,
There are a few practical considerations. With versions before ArchiCAD 18 an assumption was made that the time to create a TCP connection would seldom exceed 1 second. This is the case for private networks, but wide area networks can have delays that can sometimes push the TCP connection establishment time above 20 seconds. Above 20 seconds the ArchiCAD client assumes the server is offline. Additionally, a TCP connection that is broken will require the client and server to restart the data communication from the start. Over the Internet TCP connections break with more frequency than they do in a private network.
Large data set transfers like a library or a join, might need multiple tries before successful completion when done over the Internet. Where a small project with an optimized library may work superbly for 40 users a larger weight project may be dismal with 1 user. (Note number of users isn't really a concern, it is the project and library size in MBs that matter)
There are other practical considerations. The installer wasn't designed around cloud services; you’re bound to run into a few glitches. Each BIM Server module uses 3 ports, which will need to be opened – not just the http port as is the case for most web servers. The BIM Server’s speed is highly dependent on the speed of access of data. What might be the cost for an acceptable quality of service on storage? What might be the cost of opening ports? What might be the cost per data transfer?
In ArchiCAD 18 we are testing the software in cloud environments. ArchiCAD 18 is prepared to cache data to remote sites to reduce byte transfer costs and work around unreliable network issues.
I’m sure what you want to do can be done. I’m not sure it will perform to your expectations. I believe what you will really want is in ArchiCAD 18…. patience….it will be here soon.
Graphisoft Technical Support