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

4 results

Diagram of an integration showing time limits, cancellation, and recovery of a pending operation

Integraciones, APIs y sistemas conectados6 min

Integrations with Time Limits: How to Design Timeouts and Cancellations That Protect Business Processes

Set how long each integration can wait, decide what happens when the limit expires, and recover uncertain outcomes without duplicating actions or leaving processes stuck.

↗

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.

↗

Conceptual diagram of an exception queue in an automation with human review

Automatización, datos e IA7 min

Exception queue: automations that stop, explain, and regain control

Design an exception queue to stop, explain, and recover automations with human control, traceability, and safe actions.

↗

Data contract diagram between integrated systems

Desarrollo de software6 min

Data Contracts: How to Prevent Integrations from Breaking When Systems Change

A guide to defining verifiable data contracts, managing changes, and detecting incompatibilities before they affect integrations.

↗