DZone.com Feed

Portable Intelligence Architecture: When the Runtime Becomes the Hard Problem

2 Sep 2026, 19:00 by Punit Shah

For two decades, we focused on moving data to the intelligence. Now, we’re seeing a massive shift: we have to move the intelligence to the data. That flip changes everything. Your host platform isn’t just an API gateway anymore; it’s an operating system.

The Meeting That Wasn’t About Models

The meeting that changed how I think about AI infrastructure had almost nothing to do with models. We spent months obsessing over model quality. Then, over a few weeks, the agenda quietly reorganized itself. We were talking about onboarding third-party units. We debated what happens when two versions of the same model disagree under replay. We worried about whether one tenant’s inference could starve a neighbor’s on a shared accelerator. We fought over who pays for a millisecond.

‍

Extracting Entities and Relationships From Engineering Documents With spaCy

2 Sep 2026, 18:00 by Sriharsha Makineni

Engineering teams generate a lot of useful knowledge, but most of it is locked inside text.

A service ownership note may tell you who owns an application programming interface (API), while a runbook may tell you which database a service relies on. An incident review may detail how one fault impacted the other systems. Each of these is individually useful. It’s when we are able to link together all of these facts that we get our greatest value.

‍

Best Practices for Handling Bad Data in Stream Processing Platforms

2 Sep 2026, 17:00 by Gautam Goswami

Today, stream processing platforms facilitate the real-time analysis of data flowing continuously from Internet of Things (IOT) devices, financial transactions, web applications and servers at banks, manufacturing equipment, logistical systems in warehouses and ships, as well as customer activities with conversational agents on web portals. Streaming frameworks like Apache Kafka, Apache Flink, Apache Spark Structured Streaming, and stream databases are empowering business folks to process millions of events in real time.

But what your streaming platform is worth depends exclusively on the quality of data fed into it. An event that is malformed, a duplicate message, any missing field, or an invalid timestamp can lead to incorrect analytics generation, false alert triggers, bursts of alerts, and even application crashes. Batch processing allows for data to be cleaned before execution, but stream-processing requires that validation and corrections occur while the data is flowing. Thus, establishing a strong data quality strategy is a core necessity of any event-driven architecture.

‍

Shift-Left Without Losing the Audit Trail: Test Automation for Regulated Surgical Software

2 Sep 2026, 16:00 by Dimple Bajaj

In most software, a red test is a bug. On the systems I work on, a red test can be a patient-safety signal. That one difference reshapes almost every decision you make when you sit down to design a quality strategy.

I've spent more than a decade in software quality, most of it around medical device software: robotic-assisted surgery, surgical simulation, and clinical education platforms. The engineering is interesting on its own. What makes it genuinely hard is that every test, every pipeline, and every release has to satisfy two audiences at the same time. Engineers want fast feedback. Regulators want traceable evidence that the software does exactly what its requirements say, and nothing dangerous besides.

‍