Hi Placide;
That is an excellent idea for your DBMS! The cloud is basically a fancy name for the old "service bureau" term. Cloud providers can house your DBMS on their platform. You can then expose the DBMS via its Cloud IP address. This would normally be done by creating an O/S instance (ie: MS-Windows Server edition). I myself personally use Amazon's EC2 feature to host my SA & SS DBMS. Most cloud vendors offer the same. Once the instance is built, its assigned an internal IP address.
The next thing I did was to create an Amazon "Elastic" address. This allows the cloud vendor to assign a fixed IP address that is externally visible. It also allows for the EC2 virtual machine to be restarted on any other VM where the IP address is different. However, Amazon always keeps the Elastic IP address pointing to the ever changing internal EC2 machine's IP address. That way, your PB App only needs to connect to (know about) the external Elastic IP address.
In the case of the Elastic IP address that gets redirected internally - your App really only needs to know what "port" your DBMS is listening to in order to complete the DB connection. In the case of my SS's its port 1433. Note that many other vendors implement this "Elastic" IP concept (ie: RackSpace, IBM. etc).
FYI: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/elastic-ip-addresses-eip.html
HTH
Regards