Trendora

Distributed systems

Trial

Techniques

A system design approach for coordinating reliable behavior across multiple components.

Why it's here

Placed in Trial: 9 article(s) of evidence from 3 source(s), led by research-stage coverage, with 2 in the last 30 days. Confidence 67%.

Evidence (9)

  • 4InfoQ·10/6/2026product_launch
    QCon London 2027 Unveils 15 Tracks on Production AI and Engineering at Scale

    InfoQ previewed the QCon London 2027 program, which will span 15 tracks focused on production AI, architecture, distributed-systems debugging, modern data platforms, high-performance engineering, and Staff+ leadership. The agenda highlights practical topics such as agent evaluation and guardrails, reflecting current priorities for building and operating large-scale software systems.

  • 3Hacker News·9/14/2026research
    Distributed systems classic papers

    This Hacker News item shares a curated list of classic and influential distributed systems papers, including foundational work on time, consensus, replication, snapshots, and CRDTs. It is presented as a starting point for understanding the field rather than a new technical release or product announcement.

  • 4InfoQ·8/19/2026framework_update
    Avoiding Cascading Failures in Distributed Systems

    Sam Newman explains progressive collapse from civil engineering and relates it to failure propagation in distributed systems. He uses examples such as the Ronan Point tower collapse and AWS outages to outline resilience practices like strengthening components, isolating failures, and reducing interconnections.

  • 5InfoQ·8/5/2026research
    JioHotstar Details Distributed Ad Request Engineering for Streaming Scale

    JioHotstar describes the distributed architecture behind its real-time ad request pipeline for streaming playback. The system combines ad decisioning, waterfall tiering, pacing algorithms, latency optimization, and service coordination to select and serve personalized ads at scale.

  • 4InfoQ·7/30/2026research
    The Rise of Disaggregated Cloud Databases

    Murat Demirbas describes how cloud economics are pushing database systems toward disaggregated architectures that separate compute from storage. He highlights benefits such as elastic scaling, lower cost, and better fault isolation, and examines related design ideas including Paxos, shared-memory evolution, and self-assembling databases.

  • 4InfoQ·7/17/2026research
    CNCF Says Cloud-Native Infrastructure Will Underpin Agentic AI

    A technical analysis from the Cloud Native Computing Foundation argues that agentic AI will likely run on the existing cloud-native stack rather than entirely new infrastructure. It frames cloud-native technologies as the foundation for building trustworthy, distributed AI systems.

  • 4Hacker News·7/15/2026research
    Mysteries of Telegram Data Centers

    This article investigates how Telegram organizes and operates its data centers, focusing on the platform’s infrastructure choices and the uncertainty around its architecture. It discusses observations and inferences about Telegram’s distributed backend rather than a formal company disclosure. The piece is of interest mainly for its technical analysis of large-scale messaging infrastructure.

  • 5Martin Fowler·7/14/2026research
    DSLs Help LLMs Produce Reliable Code

    The article argues that large language models are most reliable when constrained by clear abstractions and domain-specific languages, rather than asked to implement everything from a broad natural-language spec. It uses Tickloom as an example of building and then using a DSL for distributed system behavior, with LLMs acting both as a design partner and a natural-language interface.

  • 6Hacker News·7/2/2026research
    Postgres transactions as a workflow superpower

    The article argues that workflow state and application data can live in the same Postgres database, allowing both to be updated in a single transaction. This removes failure windows that cause duplicate side effects, simplifying idempotency and enabling exactly-once execution for transactional workflow steps.