If these microservices have the same or similar content of strings, then you can have all the content stored under the same project. You can have a different resource for each microservice and create categories for each one based on the microservices they belong to. More information about the categories feature can be found in our documentation guide here.
However, if you would like to keep the content in different projects (you can create unlimited projects), you can still do that. This would be a better option if:
The content of each microservice will be translated into different languages (e.g., Microservice A will be translated into French and Spanish, and Microservice B will be translated into Turkish and Greek).
The content of each microservice should be localized based on a different localization workflow (e.g., Microservice A will be translated using Machine translation while Microservice B will be translated using a vendor, Microservice A will be translated using GitHub Integration while Microservice B will be translated using Zendesk integration, etc.)
You have defined a different voice, tone, direction, and style for each microservice, meaning you might need a different glossary, style guide with instructions, etc.
If you decide to move on with different projects for any of the above reasons but still want these projects to share the same translation memory suggestions, then you can use TM groups. That way, you can ensure that previously translated content of a localization work already done for one project will be used in any other project of the same group.
💡Tip
Looking for more help? Get support from our Transifex Community Forum!
Find answers or post to get help from Transifex Support and our Community.