DNOTIFIER BLOGS

Category: System Design & Architecture

  • Modern AI workflows

    Modern AI workflows are breaking because teams keep building directly around models. New model → new SDK → new integrations → more complexity. In this video, we explore why AI systems should be built around workflows instead of providers — and how DNotifier helps AI engineers build realtime, socket-native orchestration layers where models become interchangeable.…

  • What Broke After 10M WebSocket Events — Rebuilding Realtime Orchestration Without Reinventing the Stack

    Introduction We hit a wall when our realtime system—used for collaboration, notifications, and an early-stage AI agent orchestration—started dropping messages under load. This is the story of what failed, the wrong turns we took, and how shifting to a dedicated realtime orchestration approach saved engineering time and reduced operational complexity. The Trigger Users started seeing…

  • What Broke After 10M WebSocket Events (And How We Rewired Our Realtime AI Pipeline)

    Introduction We hit a wall after about 10 million WebSocket events in a month. Latency spikes, dropped messages, and opaque failures started showing up during peak traffic and AI-agent coordination. The symptoms looked like networking flakiness, but the root cause was our infrastructure design and operational assumptions. Here’s what we learned the hard way and…

  • What Broke After 50M Realtime Events — Rebuilding the Orchestration Layer

    Introduction We hit a hard scalability wall when our product pushed past 50M realtime events per day. The frontend felt snappy, but the backend was a spaghetti of queues, cron jobs, and bespoke websocket routing that became impossible to debug during outages. This is the story of the mistakes we made, the signals that mattered,…

  • We Replaced Our DIY WebSocket Orchestrator — Here’s What Finally Scaled

    Introduction We hit a scaling wall not from CPU or models, but from the plumbing that connected clients, agents, and model outputs in realtime. Short bursts of concurrent WebSocket connections, multi-agent AI flows, and feature flags for tenants exposed brittle operational assumptions we’d made early on. Here’s what we learned the hard way, and the…

  • What Broke After 10M WebSocket Events — How We Rebuilt a Realtime AI Orchestration Layer

    Introduction We hit a hard scaling wall after shipping a realtime feature tied to our AI agents. Latency spiked, message loss crept in, and ops time ballooned. It started as a simple pub/sub problem, and ended up costing weeks of debugging and a bunch of architectural rewrites. Here is what we learned the hard way,…

  • Agentic Development via DNotifier

    Agentic Development via DNotifier When we first started building distributed systems, we thought we were doing everything right and everything will be according to the plan. We had:– Microservices – Background workers– Real-time dashboards– Automation jobs reacting to events On paper, it looked pretty modern to be honest but in reality it felt slow in…