Convert code to another language for IT & Software

You are an expert in this kind of work, and you know the IT & Software sector from the inside.

## Your task
Convert this [SOURCE LANGUAGE] code to idiomatic [TARGET LANGUAGE] for a team at a software company that ships a SaaS product. Use the target language's standard libraries and conventions, keep behaviour identical, and list any behaviour that cannot map one to one.

## About my situation
- Who this is for: engineering leads, developers and IT buyers
- What we must respect: uptime, security and data-protection requirements
- How we measure success: deployment frequency and uptime

## What matters in IT & Software
- Rules and standards that usually apply: data-protection law (GDPR in the EU, the DPDP Act 2023 in India, CCPA in California); SOC 2 or ISO 27001 security audits; OWASP secure-coding practice; open-source licence terms; the uptime and support promises in customer SLAs.
- Common risks to plan for: outages; data breaches and security holes; vendor lock-in; scope creep; knowledge held by one person; churn after a bad release.
- Tools commonly used: GitHub or GitLab; Jira; Slack; AWS, Azure or GCP; Datadog or Grafana; PostgreSQL or MySQL.
- Words people in this field use: SaaS; multi-tenant; SLA; incident; sprint; release; tech debt; API; ARR.
- Rules differ by country. If I have not said where I work, ask me, and do not present one country's law as if it applied everywhere.

## What I will give you
Code:
[PASTE CODE]

## How to work through it
1. Explain what the original code does.
2. Map each part to the target language's idioms and standard library.
3. Write the converted code.
4. List behaviour that cannot be translated one to one and how you handled it.
5. Suggest tests to prove both versions behave the same.

## What to deliver
- Converted code
- Mapping notes
- Differences list
- Test suggestions

## Rules
- Make every point specific to my situation and my industry; replace generic advice with detail that fits.
- Use plain language, short sentences, and tables where they make the answer easier to scan.
- Use only the facts I give you. Do not invent figures, laws, sources or quotes. Mark anything you had to assume with "Assumption:".
- If something important is missing, ask me up to 3 short questions before you start.

## Before you answer
Check your draft against this list and fix anything that fails:
- The code works as written: no invented libraries, functions or APIs, and versions are named where they matter.
- It is written for a software company that ships a SaaS product; nothing in it would read the same for any other business.
- Nothing in it breaks uptime, security and data-protection requirements.
- Every item under "What to deliver" is included.