(评论)
(comments)

原始链接: https://news.ycombinator.com/item?id=43452793

最近Hacker News上的一篇讨论集中在软件开发中的“同步预算 (Synchrony Budget)”概念,该概念在外部文章 (morling.dev) 中有详细介绍。评论者强调了异步操作的隐藏成本,并建议“异步预算 (Asynchrony Budget)”可能同样重要。用户PaulHoule认为,异步进程带来的每个潜在的顺序紊乱实例都会增加错误的可能性,并且呈非线性增长。另一位用户bobnamob强调了同步调用的优越简洁性,这使得系统更容易推理和设计。他们提倡默认采用同步通信,除非特定的性能约束需要异步方法,优先考虑可管理性和可理解性,而不是潜在的微小延迟改进。这场讨论突出了在同步和异步架构之间进行选择时,性能提升和复杂性之间固有的权衡。

相关文章
  • 同步预算 2025-03-27
  • (评论) 2024-07-14
  • (评论) 2024-03-26
  • (评论) 2023-12-31
  • (评论) 2024-02-26

  • 原文
    Hacker News new | past | comments | ask | show | jobs | submit login
    The Synchrony Budget (morling.dev)
    4 points by ingve 2 hours ago | hide | past | favorite | 2 comments










    You might as well have an “asynchrony budget” since each point of disorder (where events could happen in a different sequence) is a place where an error could happen and the trouble scales worse than O(N) where N is the number of asynchronous processes.


    Agreed, I feel like the article didn't address the other major benefit of sync calls, namely their simplicity.

    A system built on purely synchronous calls is infinitely easier to reason about and design in all aspects other than e2e latency.

    I'd almost approach from the opposite direction, defaulting to sync calls till you have concrete performance reasons not to.







    Join us for AI Startup School this June 16-17 in San Francisco!


    Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact



    Search:
    联系我们 contact @ memedata.com