Asynchronous Job Localization Using Pre-Generated Locale Data
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
SaaS platforms face challenges in presenting asynchronous job data in the language of the locale where it is consumed, as the data is not immediately consumed and must be persisted, and existing translation methods introduce unwanted coupling or require review-approved translations, especially when the data includes parameters referencing other information.
Innovation Solution
The solution involves generating data objects for asynchronous jobs in multiple review-approved languages at the time of invocation, storing these objects in a jobs management service, and selecting the appropriate instance based on the client's locale, or using callbacks or pre-stored message catalogs to translate data at the time of consumption.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If data objects are generated in multiple review-approved languages at the time of invocation and stored in the jobs management service, then the correct language can be presented to the client based on locale, but storage requirements increase
Solution Approach 1:
The patent applies preliminary action by generating data objects in multiple review-approved languages at the time of job invocation, before the job is executed and before the client consumes the output. This allows the localization to be prepared in advance and stored with the job data, enabling the jobs management service to later retrieve and present the appropriate language version based on the client's locale without needing to perform translation or selection at consumption time.
2Quantity of substance
If translation is performed at the time of consumption using callbacks or pre-stored message catalogs, then storage requirements are reduced, but response time increases
Solution Approach 1:
The patent resolves this contradiction by performing the translation action preliminarily - at job invocation time rather than at consumption time. The data objects are created in multiple languages and stored with the job, so when the client consumes the output, the appropriate language version is already available for immediate retrieval, eliminating the time delay that would occur with on-demand translation.
3Adaptability or versatility
If existing translation methods are used, then language localization is achieved, but unwanted coupling is introduced
Solution Approach 1:
The patent applies segmentation by separating the localization functionality into distinct data objects that are generated and stored independently. Each data object contains language-specific information as a separate entity, allowing the jobs management service to handle localization without being coupled to specific translation mechanisms or language processing logic. This modular approach eliminates unwanted coupling between the core job execution functionality and the localization subsystem.
Data Source
AI summary
Architectures and techniques are described that can provide localization for asynchronous jobs. The content generated by an offer service of a software as a service (SaaS) platform from an asynchronous job can be persisted by a jobs management service. The jobs management service is not the owner of the data, but can provide language localization appropriate for the client locale that is requesting the persisted data. Such can be accomplished by numerous approaches, including an approach that instructs the offer service to transmit localization data at the time of content generation, which can be persisted by the jobs management service.