Language CDN

CDN is an abbreviation for Content Delivery Network. At its core, it’s a network of servers also named Points of Presence (PoPs) that store replicas of content in their memory (cache) and then deliver it to requesting users. The geographic location determines this delivery to connect the user to the nearest and fastest server, reducing data transfer time (latency).

Localazy CDN delivers the up-to-date translations reliably and directly to the distributed version of your project, without the need of having to download and update the translation files every single time you make a new release.

Learn more about Localazy CDN in the documentation.

To use Localazy CDN, you first need to activate Online Services in the Localazy Marketplace.

Then, head to the File management section of your app at Localazy and click on the CDN button (looking like a chain link 🔗) to obtain your file URL.

With this URL, you can set up the CDN in your project. Depending on the platform of the project, the implementation method will differ.

For a detailed implementation example of Localazy CDN read our article: Deliver translated files seamlessly via Localazy CDN

Your Localazy CDN usage costs will depend on consumed resources every month. We count the number of HTTPS requests, the volume of data transferred, and how many times your changes were published across the network.

If your translation file has ~20 kB, you make 50 changes during the course of the month, and our CDN delivers it to 10,000 users per month, the total cost will be as follows:

• Data transfers (10,000 * 20kB) * $0.5/GB = $0.095
• HTTPS requests (10,000 / 1000) * $0.005 = $0.05
• File management 50 * $0.01 = $0.5

Total price per month: $0.645

Learn more about the pricing structure of Localazy CDN in the documentation.

Along with your translated files, the so-called metafiles are also available through the CDN - you can get them in JSON, Javascript, or Typescript.

Metafiles contain additional information that can help you, e.g., make the language selector in your product completely manageable from within Localazy, allowing you to add new languages asynchronously.

From the metafile, you can get:

• filename and path for each of the files
• all languages for each of the files, including:
• locale code
• English and localized name
• URL to CDN for each of the languages
• function for resolving plural form (in JS/TS file)
• timestamp of the last update

There are several benefits to using Localazy CDN. Let’s view the Localazy CDN from the perspective of developers, users, and, most importantly, yourself.

Saves time for developers 🔗

Automation saves your development team precious time. Localazy CDN effectively shortens the release cycle and reduces the room for error because it takes one of the variables out of the equation! Once you have everything set up, you won’t have to worry about releasing new languages into your online product.

Localazy CDN is also compatible with different releases of your localizable files in Localazy. All your release tags are automatically available so that you can serve the fresh files for your testing, and once you are sure of their quality, you can push them to production.

Instant worldwide coverage for your users 🔗

Serve your users freshly translated content in a matter of minutes. All changes published in Localazy will propagate across all CDN points of presence in minutes. Users are always served the file from the closes geographical location, making the load times shorter and the experience more seamless.

Scales with your project and saves you time and money 🔗

Our CDN is built on proven and scalable technologies, so you don’t need to worry about whether you have ten or ten million users. You can start using the CDN for under $1/month and always keep track of your costs on the dashboard. We serve terabytes of data and hundreds of millions of requests monthly. Localazy CDN is infinitely scaleable and grows with your business.

Your localization files are stored on Amazon S3, providing an impressive 99.99% uptime. Everything is then delivered through Amazon CloudFront, a distributed CDN that makes it incredibly reliable.

All files are cached and delivered globally through multiple data centers. Even if some of the networks experience issues, the data is still accessible on different nodes, meaning your end users won’t encounter any severe downtime.

If reliability is your top priority, you can contact us for details of making the translation delivery even more resilient as part of the Enterprise plan. We’ll make sure to help you achieve the best results.