Every single company I have worked with have needed to translate small pieces of text into multiple languages. This is typically done with a simple database structure, containing one table declaring the supported languages, and another table containing translated entities. The database structure itself is ridiculously simple, and so is its main web API. Two simple endpoints, one returning supported languages, and another returning all entities in a single language. The latter typically has a key/value structure, allowing the frontend to replace all occurrences of a specified key with the value for that specific key.

The problem isn’t as much the micro service itself, as the administration of languages and translations. The average enterprise app might easily have hundreds and sometimes thousands of such small translations entities, typically translated into half a dozen languages, and typically creating an administrative dashboard for managing such things is not high priority, because it’s not the “bread and butter” technology of the company itself.

Babel Fish is one of our micro services that you can install through our Bazar. Babel Fish allows you to declare your supported languages, and then as you create individual entities, it gives you the option of populating all other languages with default values, automatically translated by invoking Google Translate. This results in 98% accuracy, before you send the entities to native speakers to translate them into all supported languages, eliminating 98% of the workload and freeing up energy for these to focus on slightly “more important stuff”

Notice, I have worked for dozens of companies in my career, and 80% of the companies I have worked for, have had more or less the exact same structure for translations. It’s a well known design pattern for translating apps, both web apps and smart client apps. One database, two endpoints; get-languages and get-translations – And sure, it’s not really rocket science to be honest with you, but it’s not the “rocket science” that’s typically your problem. The stuff that eats up your company’s profit are the small things. The things nobody really cares about, because it’s “not important enough”. Well, for us that is the important stuff. Below you can see a screenshot of how the administrative dashboard looks like.

Realise, the above web app contains roughly 10,000 lines of code in total, implying a single developer would need several months creating it from scratch. A single developer will cost you at least €5,000 per month, implying the TCO of creating the above yourself becomes at least €10,000. We sell it as an “out of the box” solution for 1/20th of that cost, and you get all its source code and free updates, and it takes you less than 5 minutes to install it as a micro service using Magic’s Bazar.

To get started with Babel Fish, first install Magic. Then visit its Bazar and purchase the Babel Fish module. 5 minutes later you’ve got its backend module. Then deploy its frontend dashboard on a VPS or something, and you’re done. The frontend contains a “docker-compose.yml” file making installation of the frontend very easy. To see me demonstrating its frontend you can check out the following video.

Leave a Comment

Your email address will not be published. Required fields are marked *