The Challenge

2000 files in English that need to be processed into 25 languages. 1+1 = 50,000 deliverables per push. The volume by itself was a huge issue but it was far from the only one. Each of these files also have complex structures with a web of keys, variables and tags that need to be meticulously mapped out and monitored for a successful implementation.

BWX was built for enterprise-grade large scale connectors

Enterprise-grade implementation ranges from complex to nightmarish. The final mile where the tech meets the use case is the difference between victory and defeat. Our implementation team working with Coupa Software blends developers with solution architects that have hands-on experience as project managers and localization engineers. This creates an edge that allows us to relate to the actual business and pains as opposed to purely talking about what’s possible and. not from a feature perspective. When we BWX implements, it’s a same-side collaboration.

With large scale connectors you need to focus on all key areas involving localization management:

  • aggressive file engineering for optimized parsing and segmentation
  • focus on performance and load management to scale pain-free
  • an error-tolerant process that allows to troubleshoot specific deliveries that may have malfunctioned
  • strategic brainstorming and innovative approach

“With over 50,000 deliverables you can’t have a hit or miss process. API time-outs, file exceptions, and other situations are a part of such a complex process. The key is to have mechanisms in place that make it easy to understand where something failed and clarity on how to fix those files.” Henrique Cabral, BWX CTO.

50,000

Files Delivered with Every Push

Most importantly with a framework built to handle 500,000 files if necessary

99.8%

Job Delivery Success Rate

Even with an error-tolerant process, the native success rate conveys the solidity around the BWX solution.

25

Locales

The BWX GitHub Connector is set to process files in 25 locales in this use case but BWX can handle 100+ locales.

“The idea isn’t to sell our clients connectors. The idea is to deliver peace of mind through a solid and predictable connector framework.”

Gabriel Fairman

BWX CEO

Monitoring Strategies

One of the most important aspects of a solid connector is the automation that creates new localization tasks when the content in the repository is added or changed.

  • Branch monitoring approach

  • Pull-requests

  • Custom approach

BWX monitors GitHub repositories using its REST API. In order to do so, our clients need to authorize an account to create a token in Bureau Works to access the API. These credentials are encrypted with AES 256 and stored in the Client’s profile.

There are two monitoring strategies: branches and pull requests.

Branches:

The Connector will constantly monitor one or more branches in one or more repositories, and once the files being observed are modified, it will create a project in Bureau Works and notify our team. In continuous localization projects, any previously translated strings are fully taken into account.

Once a project is delivered, the GitHub Connector will create a Pull Request for a patch branch containing the file(s) after the translation is finished. We can customize the output path and naming strategies for the output files. This creates a non-intrusive and very elegant delivery mechanism when a team tends to use one or just a few branches for development.

Pull Requests:

Just like the Branch strategy, we can also monitor Pull Requests, for teams using Gitflow or similar workflows. The Connector can monitor all pull requests, for all the branches, for the same configured files. Again, once a difference is found based on the file’s hash, a project will be created.

The big difference with this strategy is the delivery mechanism. Because pull requests refer to a branch, once a project is delivered, the Connector will create a commit in the same branch as the pull request. Once the pull request is accepted and merged, it will carry along the translated file(s) onto the target branch, i.e., master, develop, etc.

Maximize your localization efficiency

Don’t let complexity become proportional to pain. Complex can be pain free.

Traffic

Make things scalable

Don’t wait for things to become large and out of control. Start with the tech and partnership that will set you on the correct vector for scalability.

Sales Chart

Conclusion

BWX is able to take highly challenging scenarios and make them seem simple. It’s about having the right tech framework and an aggressive stance when it comes to implementation.

Team work is the only work that works.

BWX sees itself as a SaaS platform and as a solution. The product is only as good as it’s implementation. Nothing illustrates this premise better than a large-scale connector in action.

It’s about constant evolution

A connector is never done. It’s a living entity that needs to grow and adapt according to how the scenario changes and evolves through time. There are moving parts in terms of the content strategy, the repository architecture and versioning, BWX tech, and other components. All of these must mesh seamlessly for a connector to succeed.

“It’s all peachy when we do a demo with a few android strings going back and forth from GitHub. When we are in the tens of thousands and highly customized code, it’s a whole other story. That’s when my job gets exciting.”

Jamil Raide

Head of Product

Let’s Make Things Happen

By submitting my data I agree to be contacted