Angielski dla Cloud Architekta — słownictwo AWS, Azure i GCP

Twoja architektura jest świetna — ale nie umiesz jej obronić po angielsku

Architecture Review Board. Zagraniczny CTO zadaje pytanie: "How do you plan to handle failover between regions, and what's the expected RTO?" Twoja architektura jest przemyślana, trade-offy są uzasadnione — ale szukasz słów i tracisz wiarygodność.

Jeśli pracujesz jako Cloud Architect, Solutions Architect, DevOps Engineer, Platform Engineer lub Cloud Engineer, ten artykuł daje Ci vocabularę, której potrzebujesz na Architecture Review, incident calu i rozmowie o kosztach z management.

Infrastruktura — 10 terminów

Storage i sieć — 8 terminów

Serwisy, architektura i operacje — 10 terminów

Scenariusze komunikacji

a) Architecture Review Board — 8 zwrotów

• "We chose a multi-region active-active setup to achieve 99.99% availability."
• "The trade-off here is cost versus resilience — active-active is 40% more expensive but eliminates the failover window."
• "All infrastructure is defined as code in Terraform, so provisioning is repeatable and auditable."
• "The single point of failure was the NAT gateway — we've now deployed one per availability zone."
• "We selected a managed database service to reduce operational overhead and inherit the provider's SLA."
• "The RTO is 4 hours and the RPO is 15 minutes, which aligns with the business continuity requirements."
• "Auto-scaling is configured to handle three times our current peak load without manual intervention."
• "Security groups enforce least-privilege network access — no resource has broader permissions than required."

b) Incident response — 6 zwrotów

• "We're seeing elevated error rates in us-east-1 — initiating failover to eu-west-1."
• "The root cause is a misconfigured security group blocking traffic on port 5432 to the database."
• "All services have been restored. The incident lasted 23 minutes — post-mortem will follow within 48 hours."
• "We're hitting connection pool limits on the primary database. Scaling up the instance type as an immediate mitigation."
• "The auto-scaling group is healthy but slow to react — we're adjusting the scale-out cooldown period."
• "I'm rolling back to the previous snapshot — estimated restore time is 12 minutes."

c) Rozmowa o kosztach z management — 6 zwrotów

• "By migrating baseline workloads to reserved instances we can reduce our monthly cloud spend by approximately 35%."
• "Our current monthly cloud bill is $48k — 60% of that is compute, 25% is data transfer."
• "Spot instances are appropriate for the batch jobs because they're fault-tolerant and not time-sensitive."
• "The FinOps review flagged unused resources costing $3,200 per month — I've scheduled them for decommission."
• "I'd recommend setting up budget alerts at 80% and 100% of the monthly threshold."
• "The cost increase is proportional to the traffic growth — unit economics are stable."

Krótki dialog — Cloud Architect przedstawia projekt CTO

Terminy specyficzne dla dostawców chmury — 8

Najczęstsze błędy Polaków

1. "server" zamiast "instance". W chmurze nie ma fizycznych serwerów — są instancje. ❌ "I'll restart the server." → ✅ "I'll restart the instance / pod / service."

2. "open the port" → zbyt skrótowe. ❌ "Can you open port 443?" → ✅ "Can you allow inbound traffic on port 443 from the load balancer's security group?"

3. "the cloud is down" → zbyt ogólne. ❌ "The cloud is down again." → ✅ "We're experiencing an outage in the us-east-1 region affecting EC2 and RDS services."

4. Wymowa i użycie SLA. SLA to akronim czytany jako trzy litery: ess-ell-ay. ❌ "We have a 99.9 SLA." → ✅ "Our SLA guarantees 99.9% uptime, which translates to less than 9 hours of downtime per year."

5. "I will make a backup". ❌ "I will make a backup." → ✅ "I'll take / run / create a backup before the deployment."

Quick Reference Table

Podsumowanie

Terminologia chmurowa to dziś lingua franca każdego architekta. Niezależnie od tego czy bronisz projektu na Architecture Review Board, zarządzasz incydentem o 2 w nocy, czy przekonujesz CFO do przejścia na reserved instances — te zwroty robią różnicę.

Więcej kontekstu IT znajdziesz w artykule o słownictwie IT po angielsku. Jeśli pracujesz w środowisku programistycznym, przydatny będzie też Business English dla programistów.

Gotowe fiszki z terminologią Cloud znajdziesz w ścieżce Cloud Architect w sekcji IT & Programowanie.