Loading…
Browse by type
Problem & solution reads
Problem & solution posts on Yomu, summarised newest first.
- 928 posts
- 20 companies
The Good Stuff
Paid picks we use ourselves. Links carry a referral code — a subscription through one earns us a commission at no extra cost to you.
Problem & solution posts
How AgentFlo built AI sales agents with Amazon Bedrock AgentCore – Part 1
AgentFlo built autonomous AI sales agents to address cart abandonment, unassisted messaging channels, and severe traffic spikes across eCommerce platforms. The system uses the Strands Agents SDK alongside Amazon Bedrock AgentCore to manage intent, recommend products, and execute transactions. Incoming customer communications pass through AWS Fargate before entering AgentCore runtime, which executes model-driven agents inside isolated microVMs with stateful sessions lasting up to eight hours. Tool execution is brokered separately through AgentCore Gateway to ensure operations like cart modifications scale independently from model reasoning. This deployment model enables merchants to launch specialized conversational agents in minutes without pre-provisioning capacity or maintaining custom container configurations.
Shopify powers observability for global-scale commerce with ClickHouse
Shopify rebuilt its observability infrastructure after metrics, logs, and traces became fragmented across vendors, with unpredictable costs and limited cross-signal analysis. It created Observe, a unified platform that runs metrics, logs, traces, profiles, and exceptions on self-hosted ClickHouse, treating them as structured, time-ordered, high-dimensional events and serving roughly 50 million events per second normally and 100 million at BFCM peak, or about 110 GB/s. Kafka buffers telemetry for large synchronous durable writes, while materialized views support flexible schemas, autocomplete, typed hot keys, and identifier-based correlation; the latter reportedly makes targeted searches 10x faster. Shopify reports a 16x query improvement out of the box, exceeding 30x at peak performance, with data queryable in under a minute, and says it would likely choose ClickHouse Cloud if starting again because managed operations could reduce the self-hosting burden.
Enterprise Readiness Is Not What You Support. It Is What Your Customers Can Own
Workplace operations platform SafetyCulture previously relied on a multi-team, manual onboarding process for enterprise single sign-on setups across diverse identity providers, which created operational overhead and accounted for approximately 30 percent of engineering support tickets. To resolve these scaling bottlenecks, the engineering team integrated Auth0's Self-Service Enterprise Configuration, implementing a step-by-step wizard for OpenID Connect and custom SAML setups. The resulting workflow allows customer administrators to configure identity settings, test logins before committing, and manually toggle production activation. Moving from proof-of-concept to general availability took two months, achieving a 50 percent unassisted completion rate. Four months post-launch, SafetyCulture recorded a 60 percent reduction in SSO setup-related customer support tickets.
Multilingual Knowledge Transfer under Data Constraints via Lexical Interventions
Cross-lingual knowledge transfer is critical for training multilingual language models when target-language data is scarce and downstream tasks demand reasoning or world knowledge. Existing transfer approaches often depend on scarce resources such as large parallel corpora, translation systems, auxiliary models, or extra training phases. To address this limitation, the authors introduce LINK, a data-level intervention method that operates directly during pretraining via bilingual vocabularies. LINK swaps randomly selected words in a portion of the high-resource English corpus with word-level translations according to a specified replacement ratio. Across evaluations spanning eight languages and five model sizes, the technique delivered notable performance gains on downstream target-language tasks while achieving up to a 2x speedup in training to reach equivalent performance.
Scaling Laws for Mixture Pretraining Under Data Constraints
Scaling language models demands large volumes of data, but high-value target sources like low-resource languages and specialized domains remain inherently scarce. Practitioners frequently combine limited target data with abundant generic data, creating a balance between domain underexposure and excessive repetition leading to overfitting. An empirical evaluation across more than 2,000 language-model training runs demonstrates that mixture training tolerates substantially higher data repetition than single-source training, allowing scarce target corpora to be repeated 15 to 20 times. Researchers introduced a repetition-aware mixture scaling law that accounts for both the diminishing returns of repeated target tokens and the regularizing effect of generic data. Optimizing this scaling law offers a principled framework for calculating effective mixture configurations and practical pretraining recommendations under severe data constraints.
Progressive Refinement: An Iterative Pseudo-Labeling Approach for Mandarin-English Code-Switching ASR
Code-switching automatic speech recognition faces major performance challenges due to the scarcity of code-switching training data. To mitigate this data limitation, an iterative pseudo-labeling framework leverages a large unlabeled audio corpus to generate semi-supervised speech datasets. The system structure executes across three sequential phases: pseudo-label generation, two-stage bilingual model pre-training with supervised code-switching fine-tuning, and progressive iterative improvements. Successive refinement cycles further enhance the neural model's recognition accuracy when processing complex code-switching scenarios across alternating languages. When evaluated on the SEAME benchmark, this training pipeline achieved Mix Error Rate reductions of 6.35 percent on the devman subset and 8.29 percent on the devsge subset.
Building Menu Vision: Real-Time Dish Recognition
Yelp developed Menu Vision to help diners recognize menu items and view corresponding user-generated photos and reviews in real time using their phone cameras. The feature evolved from a two-day hackathon Android prototype into a production system deployed across iOS and Android. Client devices perform all optical character recognition, text cleanup, and dish matching locally using native machine learning frameworks, while dish metadata is prefetched upon opening a restaurant page. Backend pipelines combine partner data, reviews, and photo captions into a Cassandra database, filtering exclusively for dishes with photos. To handle optical character recognition errors and name variations, the matching pipeline runs exact matching, bidirectional substring matching, and Jaro-Winkler similarity matching.
How we think about text classification in the LLM era
Medium revisited its aging NSFW text-classification model, which had outdated code, infrequent retraining, and poorly documented training and performance history. The replacement uses an LLM prompt containing NSFW guidelines and story content, requesting a 0-to-100 score, structured output, and a short reason rather than requiring a training set. To evaluate it, the team created a curator-labeled dataset with deliberate oversampling of NSFW stories, then compared several LLMs with the legacy model using false-positive and false-negative metrics. Some models matched or exceeded the legacy model; the team selected Mixtral 8×7b based on cost and performance and ran inference in Snowflake. The post presents this as a strong fit where training data is costly, trends are relatively stable, and only distribution-eligible stories need scoring, while topic and spam models still benefit from continuously updated datasets.
A revisit of remote Spectre attacks on Cloudflare Workers
Cloudflare reassessed remote Spectre attack feasibility within Cloudflare Workers production workloads to evaluate defenses against modern stabilization techniques. The experimental proof of concept bypassed Dynamic Process Isolation (DyPrIs) by keeping invocations alive using WebSocket traffic, which also diluted hardware performance counter ratios below detection thresholds. By combining branch mistraining, cache line eviction, and speculative type confusion, researchers transiently accessed out-of-bounds memory via raw 64-bit TypedArray backing store pointers. This attack demonstrated cross-tenant data leakage reaching up to 12 bit/s with over 99% accuracy in production. In response, Cloudflare mitigated the vulnerability by integrating the V8 memory sandbox, deploying Memory Protection Keys for hardware-assisted in-process isolation, and redesigning DyPrIs to monitor active long-lived executions.
How Clario technology detects PHI/PII in DICOM images using Amazon Bedrock
Clario developed an automated PHI and PII detection solution on AWS to process thousands of DICOM image slices and PDF files in clinical trials. Medical imaging workflows require strict privacy compliance under HIPAA, GDPR, and ICH E6 guidelines across standard tags, custom vendor metadata, and pixel-burned text. To address this, the pipeline retrieves files from Amazon S3 and runs memory-intensive detection workloads on Amazon EKS backed by Amazon RDS for PostgreSQL. Amazon Textract handles optical character recognition, while Anthropic's Claude Sonnet on Amazon Bedrock classifies sensitive data using domain-optimized prompt engineering. The system identifies precise coordinates and sensitive entity types rather than directly altering files, enabling human-in-the-loop review before downstream redaction occurs.
AI-powered clinical trial eligibility and safety using Amazon Bedrock AgentCore
Manual chart review across fragmented clinical sources slows clinical trial enrollment, contributing to timeline delays and high screen failure rates. To address this bottleneck, an architecture on AWS automates eligibility and safety assessments while preserving human clinician authority. AWS HealthLake ingests and normalizes records into FHIR R4 resources, while Amazon Bedrock AgentCore orchestrates pre-screening, detailed screening, and site enrollment agents. Amazon Bedrock AgentCore Evaluations scores screening determinations using an LLM-as-a-judge approach for clinical accuracy, operational effectiveness, and safety compliance. This human-in-the-loop workflow produces structured recommendations with source citations, reducing patient matching time from days to minutes while maintaining compliance audit trails.
The Merchant Identity Gap: The Hidden Payment Data Problem
Banks face a merchant identity gap: transaction descriptors from acquirers (e.g., SBUX) often don’t match customer search terms (e.g., “Starbucks” or “星巴克”) due to script differences, colloquial aliases, and cross-subsidiary naming inconsistencies. This gap inflates support costs, degrades spend categorization, and undermines personalized financial management and AI advisors. The solution uses a semantic resolution architecture on MongoDB storing a master merchant catalog with canonical names, aliases, and vector embeddings. An escalating pipeline applies fuzzy matching, semantic vector search with Voyage AI embeddings and MongoDB Vector Search, and gen AI write-back to resolve unknown descriptors and enrich the catalog. With canonical identities indexed, customers search in their own language, and institutions power conversational AI that accurately answers queries like “How much did I spend at Starbucks last month?” across markets.
How Sony LIV uses ClickHouse Cloud to deliver live streaming analytics at billion-row scale
Sony LIV’s legacy analytics environment combined batch pipelines, Elasticsearch, BigQuery, and other telemetry stores, creating slow, costly, fragmented analysis as streaming activity reached billions of events per day. During live sports, the platform needed sub-second queries, high ingestion throughput, cost-efficient long-term storage, and horizontal scaling for sudden traffic spikes. Sony LIV consolidated these workloads on ClickHouse Cloud: client, streaming, CDN, and advertising systems send events through Amazon Kinesis and ClickPipes into a ClickHouse cluster serving dashboards, product analytics, QoE, and SRE workflows. The source reports that queries previously taking tens of seconds to minutes now run in sub-second to low-single-digit seconds, improving operational responsiveness, engineering productivity, and the handling of major live-event traffic.
BGP Role model: tracking the adoption of RFC 9234
Border Gateway Protocol route leaks occur when routing announcements propagate beyond their intended customer-provider or peer relationships, causing traffic misdirection and performance degradation. RFC 9234 embeds relationship awareness directly into BGP by establishing negotiated BGP Roles and attaching an Only to Customer (OTC) transitive path attribute to prevent unauthorized route propagation. To assess real-world adoption, Cloudflare monitored OTC attribute transmission across peer networks and discovered that 33.1 percent of IPv4 and 17 percent of IPv6 paths were missing the OTC attribute. Investigation revealed that Tier-1 transit providers AS1299 and AS3257 were stripping the attribute due to legacy defensive BGP error-handling configurations. Following direct engagement, AS1299 updated its configurations to preserve OTC propagation, whereas AS3257 continued stripping it, highlighting the necessity of broader vendor and carrier support across the Internet.
Consistency is the new latency: AI at the data layer
Autonomous AI agents depend on the accuracy of the underlying data layer because retrieved data populates the LLM context window for multi-step reasoning. In distributed architectures, standard asynchronous replication lag causes agents to ingest stale data, leading to flawed execution and self-reinforcing hallucination debt when errors are saved back to memory. To resolve this, architectures must align replication strategies with specific task truth requirements across three primary patterns. High-stakes workloads utilize Amazon Aurora with global write forwarding or native Aurora DSQL for multi-region strong consistency, while high-scale scenarios leverage DynamoDB Global Tables with conditional writes to prevent lost updates. Finally, high-velocity ingestion pipelines enforce LOCAL_QUORUM reads and writes in Amazon Keyspaces to capture critical data spikes reliably.
How to Evaluate Production AI Agents: Measure System Outcomes, Not Conversations
Evaluating AI agents solely on conversational transcripts fails when agents must invoke tools to modify external production systems. Language models can convincingly narrate that an action occurred while completely omitting the underlying tool call, leaving database or billing records unchanged. Outcome-based evaluation addresses this divergence by treating external system mutations rather than generated dialogue as the actual source of truth. Frameworks such as CRMAgentBench implement persistent, stateful environments with strict all-or-nothing validation, verifying tool arguments, execution sequence, final record modifications, and the total absence of unauthorized actions. Furthermore, measuring repeated success across independent executions using pass^k metrics exposes operational variance and inconsistency that standard single-shot scores and pass@k metrics conceal.
The prototyping tax is killing your AI roadmap
The post argues that the “prototyping tax”—delay between an AI-powered idea and a working MVP—causes initiatives to lose momentum, often because organizational context is fragmented across teams, tools, and codebases. Traditional encapsulation and siloed domain knowledge can leave agents with syntax and contracts but not business intent, making production codebases harder to navigate than personal projects. The proposed response is agentic development grounded in business semantics and governed data, with alignment occurring through working builds while CI/CD, code review, and production rigor remain unchanged. The post recommends tracking time-to-prototype, first-pass acceptance rate, and PoC-to-production rate to distinguish faster demos from durable delivery. It cites a benchmark of 401 data tasks and Abacus Insights results: 77% accuracy at roughly half the cost for a platform-native agent, plus about 40% less manual effort and onboarding to first value in roughly half the time.
How Palo Alto Networks Built a Zero
Palo Alto Networks built a new SASE Health Portal to provide real-time service health visibility for its enterprise customers. The previous architecture relied on relational databases and cloud data warehousing, which caused schema migration bottlenecks and regional lock-in. To solve this, the team deployed containerized services across multiple cloud zones in an active-active configuration. They used MongoDB Atlas as a globally replicated database, enabling automated cross-region failover and flexible document modeling for customer subscriptions. The new portal eliminates alert fatigue by allowing granular subscriptions and achieves zero relational joins for fast incident matching.
Integrations That Write Themselves
Ramp describes an approach to scaling integrations beyond what engineers can build and maintain by hand. Its agentic system lets customers describe a missing workflow integration, researches the provider’s API, requests credentials through a secure widget, writes and tests ordered API-call “recipes,” and generates a deterministic script that runs the integration after build time. An internal Integration Factory applies the same pattern to first-party connectors, producing evidence for review and opening pull requests; the post says 75 integrations have shipped this way, with work reduced from weeks or months to hours. Security controls include HTTPS and hostname allowlists, private-address rejection, isolated egress, bounded responses, business-scoped immutable recipes, and test credentials rather than customer data. The central design lesson is to use models during research and construction, keep them out of execution, and bound autonomy with verification artifacts.
Serverless vehicle tracking at scale: Bosch L.OS on AWS
Bosch Mobility Platform Solutions developed the Logistics Operating System on AWS to unify vehicle tracking across fragmented spot logistics markets. The system standardizes multiple telematics providers, disparate data formats, and diverse communication protocols into a centralized visibility layer. Orchestration is handled by a Tracking Connector running on Amazon ECS with AWS Fargate, while AWS Lambda functions act as provider-specific adapters for protocol translation. Event-driven message ingestion and streaming rely on Amazon MSK, complemented by Amazon ElastiCache for low-latency caching and Amazon DynamoDB for compliance policy enforcement. Currently operational in India with ten integrated ISVs, the platform reportedly reduces integration costs by 15–20% and lowers total tracking costs for small transporters by 25–30%.
Top topics
- Architecture834
- Performance816
- LLMs670
- Machine Learning622
- Open Source567
- AI Agents561
- AI480
- Developer Experience448
Weekly digest
The best engineering reads, once a week.