Insights

Ideas to build and operate better.

Guides, analysis and lessons on product, artificial intelligence, growth, communications and cloud.

Editorial themes

Software and SaaS development

Digital products that solve, scale and evolve.

AI, automation and data

AI systems for real-world processes.

Marketing, ecommerce and marketplaces

Demand, catalogue, partners and conversion.

Communications and customer care

Every conversation in the right channel.

Cloud, infrastructure and operations

Available, observable and ready services.

results

3 results

Diagram of an application keeping some features available and limiting others when a dependent service fails

Cloud, infraestructura y operación6 min

Graceful Degradation in Applications: What to Keep When a Dependency Fails

Decide which features to keep, limit, or stop when a dependency fails. This practical framework helps protect data, inform users, and restore service safely.

↗

Digital product interface with options to undo, restore, or correct an action

Estrategia y evolución de producto digital7 min

How to Choose Which Actions Users Should Be Able to Undo in an Application

A practical framework for deciding when to let users undo, restore, or correct actions based on their impact, recovery costs, and effects on connected systems.

↗

Diagram of an API using an idempotency key to recognize retries and prevent an operation from being duplicated.

Integraciones, APIs y sistemas conectados7 min

Idempotency in APIs: How to Prevent Duplicates Without Hiding Errors

An idempotency key lets you retry sensitive operations without repeating their effects. Learn how to define its scope, handle concurrency, and respond to errors.

↗