Urgent.News

What's breaking now, across thousands of outlets.

Tech

Gobernanza de Contratos y Evolución de Esquemas en Kafka: Prevención de Corrupción de Datos con Avro y Schema Registry

A las 03:14 AM, el pipeline de procesamiento de órdenes en tiempo real de una plataforma de comercio B2B global procesó silenciosamente un millón de eventos OrderCreated con un campo numérico reubicado de integer a string por un equipo de microservicios periféricos. Ninguna excepción se lanzó en los brokers de Apache Kafka; los productores emitieron alegremente JSON estructurado dinámicamente y…

On the night of March 10, a real-time order processing pipeline in a global B2B trading platform quietly processed one million OrderCreated events. In this event, a numeric field was relocated from integer to string. No exceptions were thrown in the Apache Kafka brokers; the producers happily emitted dynamically structured JSON, and downstream consumers continued interpreting the payload.

Twelve hours later, at the close of the accounting cycle, financial reconciliation engines reported discrepancies of multiple million dollars due to numeric precision truncations and ghost deserialization errors in analytical databases. The system had failed not due to infrastructure unavailability, but because of the complete absence of a versioned and validated data contract in the asynchronous transport layer.

Anatomy of the Failure in JSON-based Asynchronous Systems In event-driven architecture (EDA) systems on enterprise scale, adopting plain-text or JSON Schema serialization without centralized validation in write-time introduces invisible technical debt. Teams assume responsibility for contracts lies in API documentation or decentralized OpenAPI repositories.

However, in a loosely coupled microservices ecosystem governed by MACH principles, event producers evolve at different rates than consumers. When a producer decides to rename a property from totalAmount to orderTotal, or change a primitive type from float to double to prevent monetary precision loss, consumers relying on the original schema suffer catastrophic silent data corruption or controlled exception blockages (ClassCastException or JsonMappingException).

Sequence diagram shows a productor sending an incompatible payload without validation, which goes to the Schema Registry, gets a compatibility check, and is then published to Kafka with the v2 schema. The v2 schema removes a required field, leading to deserialization errors or silent business failures when consumed.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

Ingress and egress: the two gateways every enterprise agent platform needs

The question security teams keep asking Most teams moving agents from demo to production now have a reasonable answer for cognitive ingress : routing prompts across providers, fallbacks, token…

  • Enterprise agent platforms need two critical gateways: ingress and egress.
  • Egress side, handling interactions with production databases and APIs, often stalls deployments.
  • Proposed four-role map: orchestrator, worker, cognitive broker, and trust gateway + executor.

Prestigious Technion Alumni Medal Awarded to IAI Chairman Boaz Levy

The prestigious medal recognizes Technion alumni for exceptional achievements, leadership, and contributions to science, technology, industry, and society.

  • Boaz Levy, IAI Chairman, receives Technion Alumni Medal on October 26.
  • Medal awarded for exceptional achievements in science, technology, and leadership.
  • Levy led IAI to record order backlogs and financial performance since 2020.

Making legacy regexes readable — without changing what they match

A pattern like this ships in real projects every day: ^(?\[(?:[A-Za-z0-9_.-]+)\])|^(?[A-Za-z_][A-Za-z0-9_]*)\s*=\s*(?"(?:[^"\\]|\\.)*"|'(?:[^'\\]|\\.)*'|[^#\n]*)\s*(?:#.*)?$ An INI-line parser: a…

  • Legacy regexes are hard to understand due to complex structure
  • RegexTester.dev offers three readability modes: Pretty, Annotated, Minify
  • Formatting regex with x/extended flag preserves original behavior

More from Monday 26 October →