But doesn't that just put you right back into RPC-land, where you don't even know whether a method call is local or over the network, bec...
But doesn't that just put you right back into RPC-land, where you don't even know whether a method call is local or over the network, because the interface is the same? And if you take the suggested alternative of wrapping the return values in 'Future', then your interface just changed, so now the code that calls your service all needs to be rewritten. It's pretty well established that service calls are either local or remote, and the service interface should show the difference between the two, but that means means that changing a service from local to remote is always going to break its clients. That's a pain point, but it's probably better than making every service call remote by default which is what a microservices architecture does.
Posted by kyllo on Aug 26, 2014, 10:08 PM
Tags
Related issues
- (1) Because it doesn't actually solve the problem.
- Every time fossil comes up, I hear this same issue - "why is there no rebase?" And honestly, I've never been able to get this argument.
- My biggest problem with running local LLMs on my M4 Max/128GB RAM is the prefill latency.
- Biggest problem with httpx I see is authors sanity https://github.com/encode/httpx/discussions/3784 .
- There aren't many situations today that make one think: Why doesn't this business have a website?
- > IAM can stay MS That's leaving the most critical component still with a US company.
Raise real-world problems, find people facing the same issue, and discuss solutions.9,000 issues0 comments
hackernews (Network)
(1) Because it doesn't actually solve the problem.
Every time fossil comes up, I hear this same issue - "why is there no rebase?" And honestly, I've never been able to get this argument.
My biggest problem with running local LLMs on my M4 Max/128GB RAM is the prefill latency.
Biggest problem with httpx I see is authors sanity https://github.com/encode/httpx/discussions/3784 .
There aren't many situations today that make one think: Why doesn't this business have a website?
> IAM can stay MS That's leaving the most critical component still with a US company.
I am very petty about this one bug and have a very old axe to grind that this reminded me of!
Not just the edge router.
But doesn't that just put you right back into RPC-land, where you don't even know whether a method call is local or over the network, bec...
But doesn't that just put you right back into RPC-land, where you don't even know whether a method call is local or over the network, because the interface is the same? And if you take the suggested alternative of wrapping the return values in 'Future', then your interface just changed, so now the code that calls your service all needs to be rewritten. It's pretty well established that service calls are either local or remote, and the service interface should show the difference between the two, but that means means that changing a service from local to remote is always going to break its clients. That's a pain point, but it's probably better than making every service call remote by default which is what a microservices architecture does.
Comments (0)
No comments yet. Start the discussion.