Internally we use AWS CloudFront to serve published dropconfigs.
This makes our infrastructure fast and reliable.
You can be confident that, once published, your dropconfig remains available as long as most of the Internet is available.
If you use dropconfig from a web-application, your end-user will be requesting assets from Internet. In some sense, a published dropconfig is just another asset.
Web-browsers cache dropconfigs very efficiently, because we use
ETag, browser will only re-download a full dropconfig if it changed.
If you use dropconfig in a fully-packaged mobile or desktop application, which doesn’t fetch any resources from the Internet - then dropconfig will slow your app down by a few tens of milliseconds.
Try it: https://a.dropconfig.com/5861ab44-1407-453a-95cd-a1999cdf7bf0.json - this is a whole Bootstrap in JSS form, published as a dropconfig.