Skip to main content

Azure Translator and Redis

Translazor is a Blazor translation component. Your Translazor subscription gives you access to the Translazor package and licensed features.

It does not include third-party services such as:

  • Microsoft Azure Translator
  • Redis hosting or managed Redis services
  • Cloud hosting
  • Azure subscriptions or infrastructure costs

Azure Translator​

Translazor currently uses Azure Translator for automatic translation.

To use automatic translation, you need your own Azure Translator resource with:

  • API key
  • Region
  • Endpoint/configuration required by your Translazor setup

Azure Translator offers a free tier for light usage. At the time of writing, Microsoft lists the free tier as up to 2 million characters per month for Translator usage.

note

Azure pricing and limits are controlled by Microsoft and may change. Always check the official Azure Translator pricing page before estimating production costs.

Is Azure Translator included with Translazor?​

No.

Your Translazor subscription does not include Azure Translator usage. Azure Translator is a separate Microsoft Azure service, billed and managed by Microsoft.

You are responsible for creating your Azure Translator resource and monitoring your Azure usage.

Redis​

Redis is optional.

You only need Redis if you want distributed caching, for example:

  • Your Blazor app runs on multiple servers
  • You deploy to multiple instances
  • You want translated values shared between app instances
  • You want cache persistence outside a single application process

For simple projects, MVPs, local development, or single-server deployments, MemoryCache may be enough.

MemoryCache vs Redis​

Cache optionBest for
MemoryCacheLocal development, MVPs, small apps, single-server deployments
RedisProduction apps, multi-server deployments, distributed caching

Do I need to buy Redis?​

Not always.

If your app runs on one server and you do not need distributed caching, you can start with MemoryCache.

Redis becomes useful when your application scales or when you need the same translation cache shared across multiple running instances.

For most users:

  1. Start with Azure Translator + MemoryCache.
  2. Test your translation flow.
  3. Add Redis later if your production deployment needs distributed caching.

This keeps the first setup simple while still allowing you to scale later.