História: Exemplos, comparações e analogias

Nível: B2

The overall design

Architect Priya presented a high-level design for a customer-notification service. The design had an API component, a queue, and a worker. For example, a request crossed the API boundary before reaching the queue. Priya drew arrows to make the data flow visible.

Comparing components

Compared with the database, the cache responded faster but stored less. The team decided that the cache was useful for frequent reads. The worker was slower than the API but handled longer jobs. The comparison clarified why the components had different boundaries.

An analogy with a limit

Priya said that a boundary was a bit like a checkpoint. The analogy helped the team imagine which requests could pass. The difference was that the boundary also defined data ownership. They wrote the ownership rule beside the diagram.

The integration point

The message broker was the most fragile integration point. The team added monitoring for delays and failed messages. The final design was clearer because the examples never replaced the technical details.

Notas de vocabulário

• high-level design — Start with the main components and relationships.
• boundary — Explain what access, data, or ownership it separates.
• data flow — Show direction and transformation.
• integration point — Name where components meet and what can fail there.
• compared with — State the reference and comparison criterion.

Prática com a história

1. Una com For example: The data flow crosses the API boundary. It then reaches the queue.
2. Use Compared with para comparar cache e database.
3. Explique em inglês uma boundary usando a analogia de um checkpoint e acrescente o limite técnico.