• Business
  • Entertainment
  • Health
  • News
  • Sport
  • Tech
  • World
Newsy Today
news of today
Home - ML & Data Engineering
Tag:

ML & Data Engineering

Tech

Google Introduces Cloud Fraud Defense as Successor to reCAPTCHA

by Chief Editor May 16, 2026
written by Chief Editor

Beyond the Checkbox: The Dawn of the Agentic Web and Digital Trust

For years, the “I am not a robot” checkbox was the digital world’s primary gatekeeper. We’ve all been there—staring at a grid of blurry images, trying to decide if a sliver of a tire counts as a “crosswalk.” But the era of the static challenge is dying.

Beyond the Checkbox: The Dawn of the Agentic Web and Digital Trust
Google Introduces Cloud Fraud Defense

The launch of Google Cloud Fraud Defense signals a fundamental shift in how the internet handles identity. We are moving away from simple bot detection and toward a comprehensive “trust platform.” This isn’t just a brand update for reCAPTCHA; it’s a response to a world where the line between human and machine is becoming permanently blurred.

Did you know? The “Agentic Web” refers to an ecosystem where autonomous AI agents don’t just provide information, but actually reason, plan, and execute complex transactions—like booking a flight or managing a subscription—on your behalf.

The Rise of the AI Agent: A New Fraud Frontier

In the past, security was binary: you were either a human or a bot. Today, we have a third category: the AI Agent. These are sophisticated entities capable of mimicking human behavior so closely that traditional CAPTCHAs are effectively useless.

As these agents begin to handle financial transactions and personal data, the risk profile changes. We are no longer just fighting “spam bots” creating fake accounts; we are facing AI-driven identity fraud and coordinated account takeovers (ATO) that can bypass legacy security layers in milliseconds.

The future of security lies in behavioral signals. Instead of asking a user to solve a puzzle, platforms now analyze how a user moves their mouse, how they type, and the “reputation” of their device. This is the “invisible verification” Google is betting on—where security happens in the background to ensure that “friction doesn’t kill conversion.”

The Arms Race: Generative AI vs. Defensive AI

We are witnessing a classic technological arms race. On one side, attackers use Generative AI to create hyper-realistic personas and bypass rate limits. On the other, defenders use machine learning to spot patterns that are invisible to the human eye.

The Arms Race: Generative AI vs. Defensive AI
Google Introduces Cloud Fraud Defense Age of Total

For instance, a malicious AI might be able to solve a visual puzzle, but it struggles to replicate the subtle, erratic timing of a human clicking through a checkout process. This shift toward continuous authentication—verifying identity throughout the entire session rather than just at login—will become the industry standard.

Privacy in the Age of Total Surveillance

There is a tension here. To make security “invisible,” platforms need more data. They need to know your device ID, your location, and your behavioral patterns. This is why the shift in reCAPTCHA’s data model from “controller” to “processor” is so critical.

Fraud Prevention With Descope and Google reCAPTCHA Enterprise

By becoming a data processor, the responsibility shifts to the business owning the website. This allows organizations to align their security needs with local privacy laws like GDPR or CCPA. However, it also means that “de-Googled” or privacy-hardened devices may find themselves locked out of services that rely too heavily on proprietary signals for trust.

Pro Tip: For developers and business owners, don’t rely on a single vendor. Implementing a “defense-in-depth” strategy—combining tools like Cloudflare Turnstile for privacy and AWS WAF for infrastructure-level blocking—creates a more resilient perimeter.

The Competitive Landscape: Who Wins the Trust War?

Google isn’t alone in this pivot. The industry is moving toward a “Zero Trust” architecture where no entity is trusted by default, regardless of whether they are inside or outside the network.

  • Cloudflare: Focusing heavily on privacy-preserving challenges that don’t track users across the web.
  • AWS: Integrating CAPTCHA and challenge actions directly into the Web Application Firewall (WAF) to stop attacks before they even hit the application server.
  • Google: Leveraging its massive global telemetry (the “global signals”) to identify threats across billions of endpoints.

The winner won’t be the one with the hardest puzzle, but the one who can most accurately distinguish a “good bot” (like a helpful AI assistant) from a “bad bot” (a credential stuffer) without bothering the human user.

FAQ: Understanding the Future of Bot Defense

Will CAPTCHAs disappear entirely?
Likely yes, for the average user. They are being replaced by “silent” verification based on device telemetry and behavioral biometrics.

FAQ: Understanding the Future of Bot Defense
Google Next 2026 conference attendees

What is the “Agentic Economy”?
It is an economy where AI agents act as intermediaries, performing tasks and spending money on behalf of humans, requiring new ways to verify “authorization” rather than just “humanity.”

How does this affect my website’s conversion rate?
Reducing friction (removing puzzles) typically increases conversion. When security is invisible, users are less likely to abandon their carts or sign-up flows.

Is my data safer with a “Data Processor” model?
It provides more transparency. The company you are interacting with is now directly responsible for how your data is used, rather than a third-party provider using it for their own global models.

Join the Conversation

Do you think “invisible” security is a convenience or a privacy nightmare? Are you ready to trust an AI agent with your credit card?

Let us know in the comments below or subscribe to our newsletter for more deep dives into the future of the web.

Subscribe Now

May 16, 2026 0 comments
0 FacebookTwitterPinterestEmail
Tech

DuckLake 1.0: Data Lake Format with SQL Catalog Metadata

by Chief Editor May 2, 2026
written by Chief Editor

Beyond the File System: The Shift Toward Database-Driven Lakehouses

For years, the data engineering world has been locked in a battle with the tiny file problem. In traditional data lake formats like Apache Iceberg, Delta Lake, and Apache Hudi, metadata is primarily stored as files within object storage. While this approach allows for massive scalability, it often creates a bottleneck: the more your data grows, the more complex the coordination becomes, leading to sluggish metadata operations and a cluttered storage layer.

The arrival of DuckLake 1.0 signals a fundamental pivot in this architecture. Instead of scattering metadata across thousands of files, DuckLake stores it directly in a SQL database. This shift isn’t just a technical tweak; It’s a move toward a more agile, database-centric lakehouse that prioritizes speed and operational simplicity over the rigid file-based structures of the past.

Pro Tip: If you are currently managing a lakehouse with millions of small JSON or Avro metadata files, monitor your “list” and “get” request costs in S3 or Azure Blob Storage. Switching to a database-backed catalog can drastically reduce these API costs.

Ending the Small File Nightmare with Data Inlining

One of the most persistent headaches for data engineers is the overhead of small updates. In a standard object store, you cannot modify a single row; you must rewrite an entire file. This leads to a proliferation of tiny files that degrade query performance across the board.

DuckLake addresses this through a feature called data inlining. Rather than triggering a full file rewrite for every minor change, DuckLake allows small inserts, updates, and deletes to be handled directly within the catalog database. This effectively creates a hybrid storage layer where the “hot” changes live in the database and the “cold” bulk data remains in object storage.

“Data inlining is one of the flagship features of DuckLake. It basically enables performing small insert, delete and update operations in the catalog database, avoiding the proliferation of ‘the small file problem’. DuckLake v1.0 brings full inlining of updates, and deletes. This feature is now on by default with a default threshold of 10 rows.” DuckDB Team

This approach suggests a future where the line between a traditional relational database and a data lake continues to blur. By treating the catalog as an active participant in data storage rather than a passive directory, organizations can achieve near-real-time updates without sacrificing the cost-effectiveness of a data lake.

The Road to DataOps: Branching and Versioning

Looking beyond the current release, the trajectory of lakehouse formats is moving toward DataOps—applying software engineering best practices to data management. The roadmap for DuckLake v2.0 highlights a critical trend: the introduction of Git-like branching for datasets.

Understanding DuckLake: A Table Format with a Modern Architecture

Imagine the ability to create a branch of your production data, run an experimental transformation or a series of updates, and then merge those changes back into the main table only after they have been validated. This eliminates the need for expensive “staging” environments that mirror production data and allows for safer, more iterative data engineering.

Did you know? DuckLake is available under an MIT license, making it highly accessible for open-source contributors and enterprise developers alike via GitHub.

The Interoperability Standard

Despite the architectural shift, DuckLake isn’t trying to isolate itself. The inclusion of deletion vectors compatible with Apache Iceberg suggests that the future of the industry isn’t a “winner-take-all” scenario, but rather a world of interoperable formats. By maintaining compatibility with the Iceberg ecosystem, DuckLake allows users to leverage the performance of a SQL-backed catalog while remaining compatible with a vast array of existing tools like Apache Spark, Trino, and Pandas.

Practical Implementation: From Local to Hosted

For those looking to implement these trends today, the ecosystem is already diversifying. DuckLake is available as a DuckDB extension, allowing for local development and rapid prototyping. However, for enterprise-scale deployments, the trend is shifting toward managed services. MotherDuck, for instance, offers a hosted DuckLake service that handles the complexities of the catalog database and storage management.

Practical Implementation: From Local to Hosted
Data Lake Format Apache Iceberg Trino

This “serverless” approach to the lakehouse allows teams to focus on writing SQL and analyzing data rather than managing the underlying infrastructure of the catalog. As we witness more tools like Apache DataFusion and Trino integrating with these formats, the barrier to entry for high-performance lakehouse architecture continues to drop.

Frequently Asked Questions

How does DuckLake differ from Apache Iceberg?
While Iceberg stores metadata primarily as files in object storage, DuckLake stores table metadata directly in a SQL database to reduce coordination complexity and improve speed.

What is the “small file problem” in data lakes?
It occurs when frequent small updates create thousands of tiny files in object storage, which slows down metadata operations and increases API costs during queries.

Can I use DuckLake with my existing Python workflow?
Yes, clients are available for Pandas, as well as Apache Spark, Trino, and Apache DataFusion.

What is data inlining?
It is a process where small inserts, updates, and deletes are stored in the catalog database instead of creating modern files in object storage, with a default threshold of 10 rows in DuckLake 1.0.


Join the conversation: Do you think database-backed catalogs will eventually replace file-based metadata entirely, or will the industry settle on a hybrid approach? Share your thoughts in the comments below or subscribe to our newsletter for the latest insights into the evolving data stack.

May 2, 2026 0 comments
0 FacebookTwitterPinterestEmail
Tech

How Slack Manages Context in Long-running Multi-agent Systems

by Chief Editor April 28, 2026
written by Chief Editor

Beyond the Chat Log: The Evolution of AI Memory

For a long time, the standard approach to maintaining “memory” in AI agents was simple: preserve a running log of the conversation. As the user and the AI exchanged messages, the system would simply feed the entire history back into the model with every new request. While this works for a quick Q&amp. A session, it fails spectacularly in complex, long-running enterprise workflows.

Beyond the Chat Log: The Evolution of AI Memory
Chat Critics The Evolution

The problem is the “context window”—the hard limit on how much information an LLM can process at once. When a session spans hundreds of requests and generates megabytes of output, the history doesn’t just fill the window; it degrades the quality of the responses. We are seeing a fundamental shift from linear chat logs to structured memory.

Did you know? Approaching an agent’s context window limit doesn’t just stop the AI from “remembering” the start of the chat—it can actually degrade the overall reasoning quality and accuracy of the responses.

The future of AI isn’t about larger context windows, but about smarter context management. By using distilled truth and structured summaries, agents can maintain coherence over vast amounts of data without getting “lost” in the noise of a raw transcript.

The Architecture of Truth: Why “Critics” are the New Essential

One of the most significant trends in multi-agent design is the separation of execution from validation. In traditional setups, a single agent is expected to find the answer and ensure We see correct. In more sophisticated systems, such as those implemented by Slack, a “coordinator/dispatcher” model is used.

In this model, specialized agents handle specific tasks, but a dedicated Critic agent acts as a truth filter. This is crucial because, as observed in complex AI deployments, expert findings “could either be invented or grossly misinterpret the data.”

How the Validation Loop Works

  • Expert Agents: Gather data and generate initial findings.
  • Critic Agents: Review summary reports and use evidence inspection tools to assign credibility scores.
  • Strict Guardrails: To prevent the Critic itself from hallucinating, it is narrowly instructed to “only craft a judgement on the submitted findings.”

This trend toward “adversarial” internal checks ensures that only corroborated, high-credibility information makes it into the final output, effectively scrubbing hallucinations before they reach the end user.

Slack Native Multi-Agent Todo System

Scaling Complex Workflows: The Coordinator-Dispatcher Model

As we move toward more autonomous AI “workforces,” the industry is moving away from monolithic agents toward a hierarchical structure. This is best exemplified by the use of a central coordinator that manages a team of experts and critics.

To keep this team aligned, the system requires a shared source of truth. Instead of sharing the whole chat history, these systems use complementary context channels to maintain a “common narrative.”

The three essential channels for long-term coherence:

  1. The Director’s Journal: A structured working memory containing decisions, hypotheses, and observations. This “provides the common narrative that keeps other agents on track.”
  2. The Critic’s Review: A credibility-weighted list of findings based on evidence.
  3. The Critic’s Timeline: A distilled, chronological narrative that resolves conflicts by preferring the strongest sources and removing duplicates.

By separating these streams, the Director can make strategic decisions, Experts can build on established understanding, and Critics can evaluate findings objectively—all without overloading the LLM’s memory.

Pro Tip: If you are building agentic workflows, stop passing the full history array to your LLM. Start implementing a “summary” or “state” object that is updated at the end of each turn. This reduces token costs and increases reliability.

The Future of Agentic Reasoning: Distilled Truth vs. Raw Data

The broader principle emerging here is the move toward distilled truth. In the next generation of AI applications, the goal will not be to provide the AI with all the data, but to provide it with the right structured summary.

The Future of Agentic Reasoning: Distilled Truth vs. Raw Data
Chat Slack

We can expect to see this evolve into dynamic memory systems that automatically prune irrelevant information and prioritize “high-credibility” nodes of information. This allows an AI application to handle megabytes of output and hundreds of requests while remaining as sharp and focused as it was during the first prompt.

For those interested in the technical implementation of these patterns, exploring Slack’s approach to agentic applications provides a blueprint for moving from simple chatbots to robust, long-running AI systems.

Frequently Asked Questions

What is a context window in AI?
The context window is the maximum amount of text (tokens) an LLM can process in a single request. Once this limit is reached, the model begins to “forget” earlier parts of the conversation or may experience a drop in reasoning quality.

How does structured memory differ from chat history?
Chat history is a raw, linear log of every message exchanged. Structured memory is a curated set of summaries, decisions, and validated facts (like a journal or timeline) that capture the essence of the conversation without the bulk.

What is a Critic agent?
A Critic agent is a specialized AI role designed to validate the work of other agents. It inspects evidence and assigns credibility scores to findings to filter out hallucinations and errors.


What do you think? Is the “Critic” model the best way to solve AI hallucinations, or should we be focusing on larger context windows? Let us know in the comments below or subscribe to our newsletter for more deep dives into the future of AI engineering!

April 28, 2026 0 comments
0 FacebookTwitterPinterestEmail
Tech

Stripe Engineers Deploy Minions, Autonomous Agents Producing Thousands of Pull Requests Weekly

by Chief Editor March 20, 2026
written by Chief Editor

Stripe’s ‘Minions’ Signal a Modern Era of AI-Powered Coding

Engineers at Stripe have quietly launched a revolution in software development: autonomous coding agents dubbed “Minions.” These aren’t the yellow, banana-loving creatures, but sophisticated AI systems capable of generating production-ready pull requests with minimal human intervention. The implications for developer productivity and the future of coding are significant.

From Concept to 1,300 Pull Requests a Week

The Minions project began as an internal fork of Goose, a coding agent developed by Block. Stripe customized Goose for its specific LLM infrastructure and refined it to meet the demands of a large-scale payment processing system. The results are impressive. Currently, Minions generate over 1,300 pull requests per week, a figure that has climbed from 1,000 during initial trials. Crucially, all changes are reviewed by human engineers, ensuring quality and security.

This isn’t about replacing developers; it’s about augmenting their capabilities. The Minions handle tasks like configuration adjustments, dependency upgrades, and minor refactoring – the often-tedious but essential function that can consume a significant portion of a developer’s time.

One-Shot Agents: A Different Approach to AI Coding

What sets Minions apart from popular AI coding assistants like GitHub Copilot or Cursor? Minions operate on a “one-shot” basis, completing end-to-end tasks from a single instruction. Tasks can originate from various sources – Slack threads, bug reports, or feature requests – and are then orchestrated using “blueprints.” These blueprints combine deterministic code with flexible agent loops, allowing the system to adapt to different requirements.

This contrasts with interactive tools that require constant human guidance. Minions are designed to take a task description and deliver a complete, tested, and documented solution, ready for review.

Handling Complexity at Scale: $1 Trillion in Payments

The stakes are high. The code managed by Minions supports over $1 trillion in annual payment volume at Stripe. This means reliability and correctness are paramount. The system operates within a complex web of dependencies, navigating financial regulations and compliance obligations. Stripe reinforces reliability through robust CI/CD pipelines, automated tests, and static analysis.

Did you recognize? Stripe’s Minions are not just theoretical; they are actively managing critical infrastructure for a global payments leader.

The Rise of Agent-Driven Software Development

Stripe’s Minions are part of a broader trend toward agent-driven software development. LLM-based agents are becoming increasingly integrated with development environments, version control systems, and CI/CD pipelines. This integration promises to dramatically increase developer productivity while maintaining strict quality controls.

The key to success, according to Stripe engineers, lies in carefully defining tasks and utilizing blueprints to guide the agents. Blueprints act as a framework, weaving together agent skills with deterministic code to ensure both efficiency and adaptability.

Future Trends: What’s Next for AI Coding Agents?

The success of Minions suggests several potential future trends:

  • Increased Task Complexity: As agents become more sophisticated, they will be able to handle increasingly complex tasks, potentially automating entire features or modules.
  • Self-Improving Agents: Agents may learn from their successes and failures, continuously improving their performance and reducing the need for human intervention.
  • Domain-Specific Agents: We can expect to see the development of specialized agents tailored to specific industries or programming languages.
  • Enhanced Blueprinting Tools: Tools for creating and managing blueprints will become more user-friendly and powerful, allowing developers to easily define and orchestrate complex tasks.

FAQ

Q: Will AI coding agents replace developers?
A: No, the current focus is on augmenting developer productivity, not replacing developers entirely. Human review remains a critical part of the process.

Q: What are “blueprints” in the context of Stripe’s Minions?
A: Blueprints are workflows defined in code that specify how tasks are divided into subtasks and handled by either deterministic routines or the agent.

Q: How does Stripe ensure the reliability of code generated by Minions?
A: Stripe uses CI/CD pipelines, automated tests, and static analysis to ensure generated changes meet engineering standards before human review.

Q: What types of tasks are Minions best suited for?
A: Minions perform best on well-defined tasks such as configuration adjustments, dependency upgrades, and minor refactoring.

Pro Tip: Explore the Stripe developer blog for more in-depth technical details about the Minions project: https://stripe.dev/blog/minions-stripes-one-shot-end-to-end-coding-agents

What are your thoughts on the future of AI-powered coding? Share your insights in the comments below!

March 20, 2026 0 comments
0 FacebookTwitterPinterestEmail
Tech

QCon London 2026: Ontology‐Driven Observability: Building the E2E Knowledge Graph at Netflix Scale

by Chief Editor March 18, 2026
written by Chief Editor

The Future of Observability: Netflix Pioneers the “Knowledge Graph” Approach

Netflix is pushing the boundaries of observability, moving beyond traditional monitoring to a system built on interconnected knowledge. Engineers Prasanna Vijayanathan and Renzo Sanchez-Silva recently unveiled their function at QCon London 2026, detailing how a knowledge graph is transforming how the streaming giant understands and responds to issues across its vast infrastructure.

From Siloed Data to a Unified View: The Challenge of E2E Observability

Traditional observability often struggles with fragmented data. Metrics, events, logs and traces exist in silos, making it difficult to correlate information and pinpoint root causes. Here’s the core challenge of End-to-End (E2E) Observability – the ability to monitor a complex system from the user interface to the underlying infrastructure. Netflix’s approach directly addresses these issues.

The MELT Layer: A Foundation for Unified Observability

Central to Netflix’s strategy is the MELT Layer (Metrics, Events, Logs, Traces). This unified layer aims to improve incident resolution time by consolidating observability data. It’s a crucial step towards breaking down silos and providing a more holistic view of system health.

Ontology: Encoding Knowledge for Machine Understanding

But simply collecting data isn’t enough. Netflix leverages the power of Ontology – a formal specification of types, properties, and relationships – to encode knowledge about its systems. This isn’t just about the data itself, but about understanding the connections between data points. The fundamental unit of this knowledge is the Triple: (Subject | Predicate | Object), representing a single fact within the knowledge graph.

For example, a triple might state: “api-gateway | rdf:type | ops:Application,” defining the api-gateway as an application. Another could be: “INC-5377 | ops:affects | api-gateway,” indicating that incident INC-5377 impacts the api-gateway.

12 Operational Namespaces: Connecting the Netflix Universe

To manage the complexity of its infrastructure, Netflix utilizes 12 Operational Namespaces – including Slack, Alerts, Metrics, Logs, and Incidents – to categorize and connect all elements. The ontology captures, structures, and preserves this information in a machine-readable format, transforming operational chaos into a structured understanding.

The Knowledge Flywheel: Continuous Learning and Adaptation

Netflix’s system isn’t static. The Knowledge Flywheel embodies a continuous learning loop. It operates through three states – Observer, Enrich, and Infer – constantly adapting and improving its understanding of the system. This flywheel is integrated with a development process utilizing Claude, where the AI proposes code changes (pull requests) that are then reviewed and merged by human engineers.

This integration of AI and human expertise is a key element, allowing for automated improvements while maintaining control and oversight.

Future Trends: Automation and Self-Healing Infrastructure

Netflix’s vision extends beyond simply understanding incidents. They aim to automate root cause analysis, provide auto-remediation, and ultimately create a self-healing infrastructure. This represents a significant leap forward in operational efficiency and reliability.

The Rise of AI-Powered Observability

The integration of AI, as demonstrated by the utilize of Claude, is a major trend. Expect to see more AI-powered tools that can automatically analyze observability data, identify anomalies, and even suggest solutions. This will free up engineers to focus on more strategic tasks.

Knowledge Graphs as the Fresh Standard

Netflix’s knowledge graph approach is likely to become a standard practice. By representing infrastructure as interconnected entities, organizations can gain a deeper understanding of their systems and improve their ability to respond to incidents.

Shift Towards Proactive Observability

The goal is to move beyond reactive monitoring to proactive observability – predicting and preventing issues before they impact users. This requires sophisticated analytics and machine learning algorithms that can identify patterns and anomalies.

FAQ

What is an ontology in the context of observability?
An ontology is a formal specification of types, properties, and relationships, used to encode knowledge about a system and its components.

What is the MELT layer?
The MELT layer (Metrics, Events, Logs, Traces) is a unified observability layer designed to consolidate data and improve incident resolution time.

What is a Triple?
A Triple is a tuple (Subject | Predicate | Object) that defines one fact in a knowledge graph.

How does Netflix use AI in its observability system?
Netflix uses AI, specifically Claude, to propose code changes and automate parts of the observability workflow.

What are the 12 Operational Namespaces?
These are categories used by Netflix to organize and connect all elements of its infrastructure, including Slack, Alerts, Metrics, Logs, and Incidents.

Did you recognize? The concept of a knowledge graph isn’t new, but its application to large-scale observability, as demonstrated by Netflix, is a significant advancement.

Pro Tip: Start compact when implementing observability solutions. Focus on identifying key metrics and events, and gradually expand your coverage as you gain experience.

Seek to learn more about modern data engineering practices? Explore our other articles on data architecture and observability tools.

March 18, 2026 0 comments
0 FacebookTwitterPinterestEmail
Tech

QCon London 2026: Behind Booking.com’s AI Evolution: The Unpolished Story

by Chief Editor March 17, 2026
written by Chief Editor

Booking.com’s AI Journey: Lessons for the Future of Data-Driven Platforms

Booking.com’s evolution from Perl scripts and MySQL databases to a sophisticated AI platform, as detailed at QCon London 2026 by Senior Principal Engineer Jabez Eliezer Manuel, offers valuable insights into the challenges and triumphs of scaling AI within a large organization. The presentation, “Behind Booking.com’s AI Evolution: The Unpolished Story,” highlighted a 20-year journey marked by pragmatic experimentation and a willingness to adapt.

The Power of Data-Driven DNA

In 2005, Booking.com began extensive A/B testing, running over 1,000 experiments concurrently and accumulating 150,000 total experiments. Despite a less than 25% success rate, the company prioritized rapid learning over immediate results, fostering a “Data-Driven DNA” that continues to shape its approach to innovation. This early commitment to experimentation laid the groundwork for future AI initiatives.

From Hadoop to a Unified Platform: A Migration Story

Booking.com initially leveraged Apache Hadoop for distributed storage and processing, building two on-premise clusters with approximately 60,000 cores and 200 PB of storage by 2011. However, limitations such as noisy neighbors, lack of GPU support, and capacity issues eventually led to a seven-year migration away from Hadoop. The migration strategy involved mapping the entire ecosystem, analyzing usage to reduce scope, applying the PageRank algorithm, migrating in waves, and finally phasing out Hadoop. A unified command center proved crucial to this complex undertaking.

The Evolution of the Machine Learning Stack

The company’s machine learning stack has undergone significant transformation, evolving from Perl and MySQL in 2005 to agentic systems in 2025. Key technologies along the way included Apache Oozie with Python, Apache Spark with MLlib, and H2O.ai. 2015 marked a turning point with the resolution of challenges in real-time predictions and feature engineering. As of 2024, the platform handles over 400 billion predictions daily with a latency of less than 20 milliseconds, powered by more than 480 machine learning models.

Domain-Specific AI Platforms

Booking.com has developed four distinct domain-specific machine learning platforms:

  • GenAI: Used for trip planning, smart filters, and review summaries.
  • Content Intelligence: Focused on image and review analysis, and text generation for detailed hotel content.
  • Recommendations: Delivering personalized content to customers.
  • Ranking: A complex platform optimizing for choice and value, exposure and growth, and efficiency and revenue.

The initial ranking formula, a simple function of bookings, views, and a random number, proved surprisingly resilient to machine learning replacements due to infrastructure limitations. The company adopted an interleaving technique for A/B testing, allowing for more variants with less traffic, followed by validation with traditional A/B testing.

Future Trends: What Lies Ahead?

Booking.com’s journey highlights several key trends likely to shape the future of AI-powered platforms:

  • Unified Orchestration Layers: The convergence of domain-specific AI platforms into a unified orchestration layer, as demonstrated by Booking.com, will become increasingly common. This allows for greater synergy and efficiency.
  • Pragmatic AI Adoption: The emphasis on learning from failures and iterating quickly, rather than striving for perfection, will be crucial for successful AI implementation.
  • Infrastructure as a Limiting Factor: Infrastructure limitations can significantly impact the effectiveness of even the most sophisticated algorithms. Investing in scalable and robust infrastructure is paramount.
  • The Importance of Data Management: Effective data management, including strategies for handling large datasets and ensuring data quality, remains a foundational element of any successful AI initiative.

FAQ

Q: What was the biggest challenge Booking.com faced during its AI evolution?
A: Migrating away from Hadoop proved to be a significant undertaking, requiring a seven-year phased approach.

Q: What is the current latency of Booking.com’s machine learning inference platform?
A: Less than 20 milliseconds.

Q: What is “interleaving” in the context of A/B testing?
A: A technique where 50% of experiments are interwoven into a single experiment, allowing for more variants with less traffic.

Q: What technologies did Booking.com use in its machine learning stack?
A: Perl, MySQL, Apache Oozie, Python, Apache Spark, MLlib, H2O.ai, deep learning, and GenAI.

Did you realize? Booking.com’s initial A/B testing experiments had a less than 25% success rate, but the focus was on learning, not immediate results.

Pro Tip: Don’t be afraid to experiment and fail quick. A culture of learning from mistakes is essential for successful AI adoption.

Want to learn more about the latest trends in AI and machine learning? Explore our other articles or subscribe to our newsletter for regular updates.

March 17, 2026 0 comments
0 FacebookTwitterPinterestEmail
Tech

AWS Launches Strands Labs for Experimental AI Agent Projects

by Chief Editor March 12, 2026
written by Chief Editor

AWS Unveils Strands Labs: A Playground for the Future of AI Agents

Amazon Web Services (AWS) has launched Strands Labs, a new GitHub organization dedicated to experimental AI agent development. This move signals a significant investment in the rapidly evolving field of agentic AI, offering developers a sandbox to explore cutting-edge approaches beyond the constraints of production-ready software.

Robots Accept Center Stage: Bridging the Physical and Digital Worlds

A core focus of Strands Labs is robotics. The Strands Robots project aims to connect AI agents directly with physical hardware. This isn’t about remote control; it’s about agents that can perceive their environment, interpret instructions, and take action autonomously. Demonstrations showcase an agent controlling an SO-101 robotic arm using the NVIDIA GR00T model, a vision-language-action (VLA) model.

The integration with LeRobot further simplifies the process of interacting with robotics hardware and datasets. This combination allows developers to build agents capable of processing visual data, understanding commands, and performing physical tasks – a crucial step towards more versatile and adaptable robots.

Simulation as a Stepping Stone: The Power of Strands Robots Sim

Recognizing the challenges of working directly with physical robots, Strands Labs also offers Strands Robots Sim. This project provides a simulation environment where developers can test and refine their agents without the risks and costs associated with real-world hardware. The simulator supports environments from the Libero robotics benchmark and integrates VLA policies, allowing for iterative experimentation and debugging.

Pro Tip: Simulation environments are invaluable for rapid prototyping and testing different agent behaviors before deploying them to physical robots. This significantly reduces development time and potential damage to hardware.

AI Functions: A New Paradigm for Software Development

Beyond robotics, Strands Labs is exploring innovative approaches to software development itself. The AI Functions project introduces a novel concept: defining function behavior using natural language descriptions and validation conditions. The @ai_function decorator then triggers the Strands agent loop to generate code that meets the specified criteria.

This “specification-driven programming” approach represents a potential shift in how software is created, allowing developers to focus on *what* they want a function to do, rather than *how* to implement it. The system automatically retries if validation fails, ensuring the generated code meets the defined requirements. The framework can generate code that performs tasks like parsing files and data transformations, returning standard Python objects.

Community Response and Future Implications

The launch of Strands Labs has generated excitement within the AI development community. Clare Liguori, Senior Principal Engineer at AWS, described Strands Labs as “a playground for the next generation of ideas for AI agent development.” Others have highlighted the potential of AI Functions to revolutionize software development workflows.

Did you know? The Strands Agents SDK, upon which Strands Labs builds, has already been downloaded over 14 million times since its open-source release in May 2025, demonstrating strong developer interest in agentic AI.

FAQ

What is Strands Labs? Strands Labs is a new GitHub organization from AWS dedicated to experimental AI agent development.

What are the key projects in Strands Labs? The initial projects are Robots, Robots Sim, and AI Functions.

What is the NVIDIA GR00T model? GR00T is a vision-language-action (VLA) model used to control robots based on visual input and language instructions.

What is specification-driven programming? It’s an approach where developers define the desired behavior of a function using natural language and validation rules, and an AI agent generates the code to implement it.

Explore the projects and contribute to the future of agentic AI at Strands Labs on GitHub.

March 12, 2026 0 comments
0 FacebookTwitterPinterestEmail
Business

Next Moca Releases Agent Definition Language as an Open Source Specification

by Chief Editor February 9, 2026
written by Chief Editor

The Rise of Agent Definition Languages: A Fresh Standard for AI’s Future

The artificial intelligence landscape is rapidly evolving beyond simple chatbots and one-off prompts. We’re entering the era of AI agents – autonomous entities capable of reasoning, utilizing tools, accessing knowledge, and orchestrating complex workflows. But with this advancement comes a critical challenge: a lack of standardization. Every platform and team defines “agents” differently, leading to fragmentation and hindering scalability. Now, a new open-source standard, the Agent Definition Language (ADL), aims to solve this problem.

What is ADL and Why Does it Matter?

Developed by Next Moca and released under the Apache 2.0 license, ADL is essentially a blueprint for AI agents. It provides a vendor-neutral, declarative format for defining everything an agent *is* and *can do*. This includes its identity, purpose, the language model it uses, the tools it has access to, its permissions, how it accesses information (through Retrieval Augmented Generation or RAG), and even governance metadata like ownership and version history.

Think of it like this: OpenAPI defines APIs, allowing different systems to communicate seamlessly. ADL aims to do the same for AI agents. As Kiran Kashalkar, founder of Next Moca, puts it, ADL is “Think OpenAPI (Swagger) for agents.”

Addressing the Fragmentation Problem

Currently, agent definitions are often scattered across various formats – YAML files, code embedded configurations, proprietary JSON fields – making it difficult to understand an agent’s capabilities and boundaries. This lack of clarity poses significant challenges for security reviews, compliance, and reuse. ADL consolidates these definitions into a single, machine-readable format, enhancing inspectability and governance.

Pro Tip: A standardized definition layer like ADL allows for consistent validation in CI/CD pipelines, ensuring agents meet predefined standards before deployment.

How ADL Works: A Declarative Approach

ADL is a declarative language, meaning it focuses on *what* an agent should do, not *how* it should do it. It doesn’t define runtime behavior or agent-to-agent communication protocols. Instead, it provides a clear specification of the agent’s characteristics, allowing different platforms and frameworks to interpret and execute it.

This framework-agnostic approach is crucial for portability. Developers can define an agent once using ADL and then deploy it across various platforms without modification. This reduces vendor lock-in and promotes interoperability.

Beyond Definition: The Future of Agent Management

The release of ADL is just the beginning. The open-source nature of the project encourages community contributions and the development of an ecosystem of tools around the standard. This could include:

  • Editors: User-friendly interfaces for creating and managing ADL definitions.
  • Validators: Tools for ensuring ADL definitions are valid and conform to the specification.
  • Registries: Centralized repositories for storing and sharing ADL definitions.
  • Testing Tools: Automated tests for verifying agent behavior based on its ADL definition.

This ecosystem will streamline the entire agent lifecycle, from development and deployment to monitoring and maintenance.

ADL and Existing Technologies

ADL isn’t intended to replace existing technologies like A2A (agent-to-agent communication), MCP, OpenAPI, or workflow engines. Instead, it complements them. ADL defines the agent itself, while these other technologies handle communication, execution, and orchestration.

Did you know? ADL focuses on the “what” of an agent, while other technologies focus on the “how.”

Real-World Applications

The potential applications of ADL are vast. Consider these examples:

  • Customer Support: Defining agents that can handle specific customer inquiries, access knowledge bases, and escalate complex issues.
  • Fraud Detection: Creating agents that can analyze transactions, identify suspicious patterns, and flag potential fraud.
  • HR Automation: Developing agents that can automate tasks like onboarding, benefits administration, and employee inquiries.

In each of these scenarios, ADL provides a standardized way to define the agent’s capabilities, permissions, and governance policies.

Frequently Asked Questions (FAQ)

Q: Is ADL a runtime environment?
A: No, ADL is a definition language. It doesn’t execute code or manage agent workflows. It simply defines what an agent is and what it can do.

Q: Is ADL tied to a specific programming language?
A: No, ADL is model-agnostic and platform-agnostic. It’s based on JSON, a widely supported data format.

Q: How can I contribute to the ADL project?
A: The ADL repository on GitHub ([https://github.com/nextmoca/adl](https://github.com/nextmoca/adl)) provides contribution guidelines and a public roadmap.

Q: What are the benefits of using ADL?
A: Portability, auditability, vendor neutrality, and improved governance are key benefits.

The open-sourcing of ADL marks a significant step towards a more standardized and scalable future for AI agents. By providing a common language for defining these powerful entities, ADL empowers developers, enhances security, and unlocks new possibilities for innovation.

Explore the ADL project on GitHub: https://github.com/nextmoca/adl

February 9, 2026 0 comments
0 FacebookTwitterPinterestEmail
Tech

Google Supercharges Gemini 3 Flash with Agentic Vision

by Chief Editor February 6, 2026
written by Chief Editor

AI Just Got a New Pair of Eyes: How Agentic Vision Will Change Everything

For years, artificial intelligence has struggled with a surprisingly human task: truly seeing. AI models could identify objects in images, but lacked the ability to investigate, to zoom in on details, or to reason about what they were looking at. That’s changing with the introduction of Agentic Vision in Google’s Gemini 3 Flash, a capability that’s poised to redefine how AI interacts with the visual world.

From Static Glance to Active Investigation

Traditionally, AI models like Gemini processed images with a single, static look. Miss a crucial detail – a serial number, a subtle sign – and the AI was forced to guess. Agentic Vision flips this script. It transforms image understanding into an active process, treating vision as an investigation. Instead of simply receiving an image, Gemini 3 Flash now plans how to examine it.

This process relies on a “think -> act -> observe” loop. First, the model analyzes the user’s request and the image. Then, it generates and executes Python code to manipulate the image – cropping, zooming, annotating – and extract more information. Finally, the transformed image is added to the model’s context, allowing it to refine its understanding before providing an answer.

The Power of Code Execution: Solving the “Hard Problems”

The key to Agentic Vision’s success lies in its ability to execute code. This allows for incredibly precise inspection of images. For example, Gemini can now reliably count the digits on a hand, a task that has historically stumped AI systems. It achieves this by drawing bounding boxes and labels directly onto the image, a “visual scratchpad” that grounds its reasoning in pixel-perfect understanding.

Beyond object counting, code execution also enables visual arithmetic and data visualization. Complex, image-based math problems can be offloaded to Python and Matplotlib, reducing the likelihood of AI “hallucinations” – those confidently incorrect answers that plague many current systems. Google reports a 5-10% accuracy improvement on vision tasks across most benchmarks as a result of this approach.

Beyond Gemini: The Future of Agentic Vision

Google’s vision for Agentic Vision extends far beyond the current capabilities of Gemini 3 Flash. The roadmap includes making the process more implicit, so the AI automatically zooms and rotates images without explicit instructions. Adding tools like web search and reverse image search will further enhance the model’s ability to gather evidence and contextualize its understanding.

The implications are significant, particularly for robotics. As one Redditor noted, Agentic Vision could unlock visual reasoning for AI in physical robots, giving them a much richer understanding of their surroundings and enabling more sophisticated agentic capabilities. While ChatGPT has experimented with similar code execution features, it still struggles with tasks like counting fingers.

Agentic Vision is currently accessible through the Gemini API in Google AI Studio and Vertex AI, and is rolling out in the Gemini app’s Thinking mode.

Pro Tip

Experiment with the “Code Execution” setting in the AI Studio Playground to see Agentic Vision in action. Try posing complex image-based questions to Gemini 3 Flash and observe how it uses code to arrive at its answers.

FAQ

What is Agentic Vision?
Agentic Vision is a new capability in Gemini 3 Flash that allows the AI to actively investigate images by planning steps, manipulating the image, and using code to verify details.

How does Agentic Vision improve accuracy?
It improves accuracy by enabling fine-grained inspection of details and reducing hallucinations through code execution and visual arithmetic.

Is Agentic Vision available now?
Yes, it’s accessible through the Gemini API in Google AI Studio and Vertex AI, and is rolling out in the Gemini app.

Will Agentic Vision be available in other Gemini models?
Google plans to extend support to other models in the Gemini family beyond Flash.

What are the potential applications of Agentic Vision?
Potential applications include robotics, image analysis, and any task requiring detailed visual understanding.

Did you know? Agentic Vision allows Gemini 3 Flash to not just *see* an image, but to actively *investigate* it, leading to more accurate and reliable results.

Want to learn more about the latest advancements in AI? Explore our other articles or subscribe to our newsletter for regular updates.

February 6, 2026 0 comments
0 FacebookTwitterPinterestEmail
Tech

Google’s Universal Commerce Protocol (UCP) Powers Agentic Shopping

by Chief Editor January 25, 2026
written by Chief Editor

Google’s UCP: The Dawn of Agentic Commerce and What It Means for Your Business

Google recently unveiled the Universal Commerce Protocol (UCP), and it’s more than just another tech announcement. It’s a foundational shift in how online shopping will work, particularly as AI-powered shopping assistants – or “agents” – become increasingly prevalent. This open-source standard aims to streamline the entire buying process, from product discovery to final payment, and it has the potential to reshape the competitive landscape for businesses of all sizes.

The ‘N by N’ Problem Solved: Why UCP Matters

For years, online retailers have grappled with the “N by N” integration problem. Every new shopping platform, every new sales channel, required a separate, often complex, integration. This was costly, time-consuming, and a major barrier to entry for smaller businesses. UCP tackles this head-on by creating a standardized “common language” for commerce. Think of it as a universal translator for shopping, allowing AI agents to seamlessly interact with any business that adopts the protocol.

This isn’t just about convenience; it’s about speed. According to a recent Statista report, global e-commerce sales are projected to reach $6.3 trillion in 2024. Consumers expect instant gratification, and UCP is designed to deliver that by eliminating friction in the checkout process.

How UCP Works: A Deep Dive into the Technology

UCP works in conjunction with the Agent Payments Protocol (AP2) and Agent-to-Agent (A2A) communication, creating a secure and flexible ecosystem. Businesses can connect via APIs, or through existing infrastructure like Shopify and Merchant Center. Crucially, UCP separates payment instruments from handlers, meaning it can work with a wide range of payment providers – Google Wallet, PayPal, credit cards, and more – without requiring constant updates.

Pro Tip: Don’t get bogged down in the technical details. The key takeaway is that UCP simplifies integration, allowing businesses to focus on what they do best: creating great products and providing excellent customer service.

The Big Players Are Onboard: Shopify, Etsy, and More

Google isn’t going it alone. The development of UCP has been a collaborative effort, with major players like Shopify, Etsy, Wayfair, Target, and Walmart all contributing. This widespread support is a strong indicator that UCP is poised to become the industry standard. Over 20 global partners have already endorsed the protocol, signaling a broad commitment to its success.

The ‘Default Economy’ Debate: Will Smaller Brands Be Left Behind?

The launch of UCP hasn’t been without its critics. Andy Reid, Chief Innovation Officer, raised a valid concern on LinkedIn: could UCP lead to a “default economy” where only one brand is surfaced as the optimal choice by AI agents? This raises the specter of larger brands dominating search results, potentially squeezing out smaller competitors.

However, James Massey, AI lead at Google, countered that UCP actually *benefits* smaller brands. By becoming “discoverable” through the protocol, smaller businesses can gain visibility without relying on expensive advertising. If their product is the most relevant, the agent can surface it, regardless of brand recognition. Massey emphasized the importance of “data quality” – ensuring accurate product information and compelling descriptions – as the key to success.

Did you know? High-quality product data is becoming increasingly important for SEO and discoverability, even *without* AI agents. Investing in accurate and detailed product descriptions can pay dividends across multiple channels.

Beyond the Checkout Button: The Future of Agentic Commerce

UCP isn’t just about simplifying the checkout process. It’s about enabling a new era of agentic commerce, where AI assistants can handle everything from product discovery to personalized recommendations to automated reordering. Imagine an agent proactively suggesting a replacement for a product you’re running low on, and completing the purchase with a single voice command.

This future is closer than you think. Google’s reference implementation already allows purchases via AI Mode in Search and Gemini, using Google Wallet or other compatible payment methods. Developers can leverage Python-based SDKs to rapidly integrate UCP into their applications, unlocking a wealth of new possibilities.

Real-World Implications: What Businesses Need to Do Now

While UCP is still in its early stages, businesses should start preparing now. Here’s what you need to focus on:

  • Optimize Your Product Data: Ensure your product information is accurate, complete, and compelling.
  • Explore UCP Integration: If you use platforms like Shopify, investigate how to integrate with UCP.
  • Monitor the Landscape: Stay informed about the latest developments in agentic commerce and UCP.

FAQ: Universal Commerce Protocol Explained

  • What is UCP? UCP is an open-source standard designed to streamline commerce on AI-powered platforms.
  • Who developed UCP? Google developed UCP in collaboration with major retailers like Shopify, Etsy, and Walmart.
  • How will UCP benefit my business? UCP simplifies integration, reduces costs, and increases discoverability for your products.
  • Is UCP secure? Yes, UCP integrates with the Agent Payments Protocol (AP2) for secure payments.
  • Where can I learn more about UCP? Visit the Google Developers Blog and the UCP GitHub repository.

The Universal Commerce Protocol represents a significant step towards a more seamless and efficient online shopping experience. By embracing this new standard, businesses can position themselves for success in the age of AI-powered commerce.

Want to learn more about the future of e-commerce? Explore our other articles on AI and retail or subscribe to our newsletter for the latest insights.

January 25, 2026 0 comments
0 FacebookTwitterPinterestEmail
Newer Posts
Older Posts

Recent Posts

  • Trump: US Doesn’t Need Deal for Iran’s Uranium

    June 5, 2026
  • Samsung Galaxy S25: One UI 9 Release Date Leaked Early

    June 5, 2026
  • We Are Still Behind

    June 5, 2026
  • Tensions Rise Between Slovakia and Hungary

    June 5, 2026
  • First Award of Kálloy Molnár Péter Prize

    June 5, 2026

Popular Posts

  • 1

    Maya Jama flaunts her taut midriff in a white crop top and denim jeans during holiday as she shares New York pub crawl story

    April 5, 2025
  • 2

    Saar-Unternehmen hoffen auf tiefgreifende Reformen

    March 26, 2025
  • 3

    Marta Daddato: vita e racconti tra YouTube e podcast

    April 7, 2025
  • 4

    Unlocking Success: Why the FPÖ Could Outperform Projections and Transform Austria’s Political Landscape

    April 26, 2025
  • 5

    Mecimapro Apologizes for DAY6 Concert Chaos: Understanding the Controversy

    May 6, 2025

Follow Me

Follow Me
  • Cookie Policy
  • CORRECTIONS POLICY
  • PRIVACY POLICY
  • TERMS OF SERVICE

Hosted by Byohosting – Most Recommended Web Hosting – for complains, abuse, advertising contact: o f f i c e @byohosting.com


Back To Top
Newsy Today
  • Business
  • Entertainment
  • Health
  • News
  • Sport
  • Tech
  • World