TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Separation of concerns between code and service layout (2010)

16 点作者 iou超过 4 年前

3 条评论

dleavitt超过 4 年前
I think the term for this is &quot;location transparency&quot; and it tends not to work well in practice. A local function call and a RPC call over a network have very different performance characteristics and failure modes; trying to abstract away the differences can be a bad scene.<p>A previous journey down this road: <a href="https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Common_Object_Request_Broker_Architecture#Problems_and_criticism" rel="nofollow">https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Common_Object_Request_Broker_A...</a>
评论 #24704030 未加载
jiehong超过 4 年前
The Erlang VM lets you move actors from your local computer to a different cluster transparently for the caller.<p>The author seems to be thinking it can be transparent at the method call site, but it’s not really the case: when executed locally, pure functions are guaranteed to return (unless hardware limitations), while remote execution necessarily brings the network issues with it; pure functions could now fail for network reasons, but only when running elsewhere.<p>Erlang works around this by forcing you to think of calls to actors as messages and to deal with all the network issues that come with it: works both locally and non locally.
chrisweekly超过 4 年前
why is this marked (2010)? I think it&#x27;s from 2020-10-04!
评论 #24703952 未加载