rdli

23 ms·

211.
by rdli 10y ago
I love hearing about the evolution of systems, and how different people have converged on the problem from different directions. [plug] I wrote a post summarizing all that I have figured out about service discovery and wish I had known from
212.
Do Multiple Implementations Make Ethereum More Reliable?(petertodd.org)
3 points by rdli 10y ago|0 comments
213.
by rdli 10y ago
Have you considered a strategy of: - engineering resilience against integration bugs directly into your architecture - setting your infrastructure up so developers can deploy develop versions of new services into production, in a way that o
214.
by rdli 10y ago
It's not about conflict resolution, it's about ordering. Imagine you have 3 services. A calls B calls C. A request goes into A. The request fails. Since there are 3 services involved, you want to be able to see the log statements
215.
by rdli 10y ago
Really, it's when you're doing microservices, and each service is deployed to a different container. Typically your business logic is now spread across multiple containers. For example, you might have a recommendation service that
216.
by rdli 10y ago
I wasn't saying you needed microservices or containers to do distributed logging. My point is that if you're building a distributed system, you need distributed logging (tracing) semantics. The actual logging mechanism (syslog, fl
217.
by rdli 10y ago
How would passing on the container ID help in mapping multiple log messages to the same request? If a request is going through multiple containers, you'll get multiple container IDs. To solve this problem, you need a unique trace ID an
218.
by rdli 10y ago
I'm surprised the article didn't mention anything about the nuances of actual logging in a distributed architecture. In particular, when a request starts to span multiple containers or microservices, you need a way to correlate al
219.
by rdli 10y ago
(Full disclosure: co-founder of Datawire) We released a microservices development kit (MDK) last week that includes similar semantics (e.g., circuit breakers, failover) that implements these semantics in Python, JavaScript, Java, and Ruby.
220.
The Hidden Dividends of Microservices (ACM)(queue.acm.org)
3 points by rdli 10y ago|0 comments
221.
Microservices Essentials for Execs: The Key to High Velocity Software Dev(forentrepreneurs.com)
1 points by rdli 10y ago|0 comments
222.
by rdli 10y ago
There aren't any good or bad answers. There are great people who haven't had a good manager. Good managers also manage not-so-great people. I ask really to understand more about their professional background. Depending on the role
223.
by rdli 10y ago
I've experienced the transition from being an engineer to a manager, and then from a manager to director, from director to VP, and now CEO. I can tell you by far the most material impact on my ability to take on more responsibility has
224.
by rdli 10y ago
To expound on the second approach listed, what I've seen is not just a service discovery layer, but client libraries (as opposed to sidecar) that connect to your service discovery (e.g., Netflix Ribbon which is EOL). Curious what peopl
225.
by rdli 10y ago
Amazon's fundamental source of competitive advantage is rarely talked about, but I think this is a great example of what that is -- they have built a company that succeeds in very low margin businesses. So they started in online retail
226.
by rdli 11y ago
Datawire | San Francisco | Boston | Backend/Frontend Engineers We're building open source infrastructure for microservices; see https://github.com/datawire/datawire-connect for details. We're passionate
227.
by rdli 11y ago
There is no valuation in this round. There is no cap. It's just a discount off of a valuation in the future. I would imagine the conversation was "the market is gyrating so much we can't agree on value" so let's def
228.
by rdli 11y ago
Early employees always get diluted. That's what happens when you raise additional capital, regardless of structure. They make up for this with a combination of a lower exercise price, the vesting clock starting earlier, and typically
229.
by rdli 11y ago
Not sure why it's so devilish. They basically raised $1B in cash on a 20% discount, no valuation cap. Basically, they're agreeing with the investors that they can't figure out a valuation for the company -- so they're de
230.
by rdli 11y ago
Ben Horowitz talks about letting people go in The Hard Things About Hard Things. Really a great book in its own right.
231.
Tim Cook Interview with Time Magazine(time.com)
3 points by rdli 11y ago|0 comments
232.
Apple's lawyer just tore into the government – here's what he said(businessinsider.com)
9 points by rdli 11y ago|0 comments
233.
by rdli 11y ago
FB made $6B in revenue in Q4 2015. LinkedIn made $862M in Q4 2015. Given the ultimate size of the global digital advertising market, it seems that there is much more growth potential in expanding share of advertising $$ than trying to expan
234.
by rdli 11y ago
The problem with LinkedIn is that they have multiple, conflicting business models each of which are too successful to kill outright. 1. They have an advertising business, that sells to marketers. 2. They have a recruiting business, which se
235.
by rdli 11y ago
gRPC bindings for languages that aren't popular at Google (e.g., Ruby, Node) aren't particularly mature. Each of the different language bindings is independently maintained, so there is no guarantee of feature parity across the la
236.
by rdli 11y ago
Great feedback! We will have Ruby in a few weeks (code is sitting on a GitHub branch), and we have Node already. Go is on the roadmap, but we also have a proxy that lets you interface with languages we don't support natively. I'd
237.
by rdli 11y ago
Live stream from the NSF: https://www.youtube.com/user/VideosatNSF/live
238.
by rdli 11y ago
If you're more worried about connection and discovery semantics, you'd want to use Datawire Connect which is built on top of Quark. Quark is being used by companies that for one reason or another need/want to build their own
239.
by rdli 11y ago
The one shortcoming of these approaches is that they are well-suited for local APIs but less so for network APIs, especially as you start to wire them together. For example, with network APIs you need to worry about stuff like rate limiting
240.
by rdli 11y ago
Here's what I've seen: 1. HTTP/JSON, with resiliency semantics layered on via SmartStack, Hystrix, or DIY library. 2. GRPC/protobuf. Haven't seen anyone other than Google run this in production, and Google doesn&#x2

More ›