Skip to the content
Page 7 of 14

Practise the new words

Exerciții de vocabular tehnic. Alegi termenii potriviți pentru a descrie probleme de cod legacy, izolat fault isolation și independența deployment-ului în echipe de inginerie.

Практика лексики для IT. Вы выбираете подходящие слова для описания проблем устаревшего кода, изоляции сбоев и независимого деплоя в командах разработки.

Practise the new words — Monolith or microservices?

Choose the right word

  • Our Denver startup managed to [outgrow / over-engineer / untangle] its original database within six months of the London launch.
  • We had to spend three weeks trying to [untangle / split out / over-engineer] the spaghetti code before we could add the new payment gateway.
  • If the main API gateway goes down, nothing works; it is a classic [single point of failure / fault isolation / big ball of mud] in our Seattle system.
  • With microservices, you gain [fault isolation / operational complexity / premature optimization] , meaning a bug in the billing service won't crash the whole application in Chicago.
  • The main benefit of microservices is [independent deployment / separation of concerns / inter-service communication] , which lets the Texas team release updates without waiting for the London team.
  • The legacy code in our Boston office has become a [big ball of mud / single point of failure / separation of concerns] where every class is connected to everything else.
  • To achieve better [separation of concerns / inter-service communication / operational complexity] , we should keep our business logic completely separate from the database access code.
  • When we migrated to microservices, the sheer [operational complexity / premature optimization / independent deployment] of managing fifty separate databases nearly broke our Dallas operations.
  • We decided to [split out / untangle / over-engineer] the notification service from our main Chicago application to reduce the CPU load.
  • Using a complex Kubernetes cluster for a simple marketing site in Seattle is a clear case of trying to [over-engineer / outgrow / split out] the solution.
  • Designing a highly scalable caching system before we even have ten active users in London is just [premature optimization / operational complexity / fault isolation] .
  • We had to upgrade our network protocols to handle the massive volume of [inter-service communication / separation of concerns / independent deployment] between our services in Dallas.

Sources: photo by Nataliya Vaitkevich on Pexels

Despre această lecție

Această lecție explorează marea dezbatere din ingineria software: alegerea între o arhitectură monolită și microservicii. Vei învăța cum să exprimi opinii puternice și să argumentezi decizii tehnice complexe în limba engleză.

Mai multe despre această lecție →

Об этом уроке

Этот урок исследует главную дискуссию в разработке ПО: выбор между монолитной архитектурой и микросервисами. Вы научитесь уверенно выражать мнения и аргументировать сложные технические решения.

Подробнее об этом уроке →

Next lessons

All Upper-Intermediate lessons →