Over the past week we’ve seen a large increase in traffic using the Babylon CDN. First we’re overjoyed that more applications are being deployed that are leveraging Babylon to bring great experiences to the world!
While this is super exciting, at the same time we want to remind everyone that the Babylon CDN is not recommended to be used in production applications. The purpose of our CDN is to serve Babylon packages to users learning how to use the platform or running small experiments. Once you’ve built an application and are ready to share it with the world at large, you should serve all packages from your own CDN.
Babylon is a victim of its success it seems.
For my part, I fetch the CDN files once with PHP and I rewrite the files locally. I find this loads scripts faster than with CDN.
With this PHP script, I call the CDN once, I copy the files locally and the CDN is no longer used on my application. It’s faster than downloading the zip
Afterwards, I find that the CDN is perhaps highlighted too much in the repository and in the docs. I mean it takes longer to download the zip (a few minutes each time) to fetch the files one by one to use them locally. Most people will only use the CDN for simplicity and speed.
what are you saying here @sebavan , that npm packages do not ever fetch remote files unless you are doing some or other runtime initialization on packages not included in the build ?
Is it alright if I download the builds (babylon.js, babylon.materials.js, Havok, Recast, etc.) once in a while (idk, every 2 weeks maybe; or after an important hotfix)?
@shaderbytes, yes, for convenience some of the dependencies are external and pointing at our cdn: like some of our wasm dependencies to workaround the need of extra setup on client builds.
This is the part we need to be extra cleat about in the doc.
PirateJC
Removed this banner . It will no longer appear at the top of every page.
12