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 a retry policy that classifies failures and routes expired messages to discard, manual review, or compensation.

Operación, observabilidad y mejora continua7 min

How Long to Retry Failed Messages: A Policy That Protects Operations

Set retry windows for failed messages according to their cause, urgency, and validity. A clear policy reduces duplicates, delays, and unnecessary manual reviews.

↗

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.

↗

Decision diagram comparing real-time integration and batch processing for connected systems.

Integraciones, APIs y sistemas conectados8 min

How to Decide Between Real-Time and Batch Integration Without Compromising Operations

Choose between real-time and batch integration based on the cost of delay, volume, available recovery options, and operational capacity.

↗