rdli

26 ms·

241.
by rdli 11y ago
protobuf and Thrift are serialization formats and an alternative to JSON, not RPC.
242.
by rdli 11y ago
Curious as to why your project is going to go with microservices? The places where everyone starts is the Martin Fowler stuff, and the Sam Newman book. Both are fine places to start. I also highly recommend the presentation by Randy Shoup f
243.
by rdli 11y ago
Can you give me an example of why you can't refactor across service boundaries? In my mind, refactoring a service interface is the same as refactoring the interface (API) of an object. It's real work (tm) but definitely do-able.
244.
by rdli 11y ago
Refactoring occurs in similar ways: with strong interfaces between each of your microservices, you can change the implementation of your individual microservices (e.g., keep the payment processing microservice interface the same, but change
245.
by rdli 11y ago
We've spent a lot of time with a lot of different companies learning about microservices and SOA. There are a ton of definitions, but the one that we've settled on and is simple is that it's an architecture that supports dist
246.
by rdli 11y ago
The problem with the premise that APIs fulfill the promise of SOA is that APIs are necessary but not sufficient to describe the interaction between two services. For example, protocol semantics such as retry in case of network failure is ab
247.
3 Questions for Startups to Answer in a Volatile Fundraising Environment(tomtunguz.com)
2 points by rdli 11y ago|0 comments
248.
by rdli 11y ago
+1 (as a founder, too). The obvious things: traction, good business plan, viable market, reputation/track record, team, etc. help. But luck and hustle are required, too.
249.
by rdli 11y ago
What kind of APIs are you trying to generate? If you're trying to do more than REST/HTTP APIs, you can check out Quark ( https://github.com/datawire/quark ).
250.
by rdli 11y ago
I disagree with the broad characterization of VC as an enemy of innovation. There are plenty of VC-backed companies that don't innovate. There are also plenty of non VC-backed companies that don't innovate either. To name 4: Googl
251.
by rdli 11y ago
This is great. It's one of the few (only?) platforms I've seen that handles both deployment and service-level concerns.
252.
What Every Startup Founder Should Know About Buying Domain Names(medium.com)
1 points by rdli 11y ago|0 comments
253.
Are microservices brewing trouble in the land of DevOps?(blog.gardeviance.org)
3 points by rdli 11y ago|0 comments
254.
by rdli 11y ago
$70K is not much in SF. Based on the economics, I'd assess based on the a) the quality of the work you'd be doing and b) the quality of the startup. To take two extremes, if you're working on creating CSS templates for a Djan
255.
by rdli 11y ago
Awesome, great to know the details (we heard about what you guys were doing second hand from Igor). Looking forward to more details whenever you post!
256.
by rdli 11y ago
You can definitely do that. There is more programming involved, since you need to figure out how to tie a new instance deployment into Chef/Puppet/etc to update HAProxy. You also need to figure out how to get it to update quickly.
257.
by rdli 11y ago
I'd argue that Homejoy's real competition is Handy, which seems to be alive and well. I'm surprised the article didn't mention Handy at all, because it is the most relevant comp for Homejoy.
258.
by rdli 11y ago
Three reasons: 1. In the central LB setup, if the LB server dies, you're service dies. Not in this setup (HAProxy is deployed side-by-side with each instance). 2. Elasticity. Imagine you have a shopping cart microservice, a search micr
259.
by rdli 11y ago
It's a fair point, so we'll clarify this (and we're working on the replication bit too). Thanks!
260.
by rdli 11y ago
We're running 1 HAProxy per application instance. The HAProxy built in health checking mechanism is designed when it front-ends > 1 app instances (i.e., it serves as a central proxy). Watson checks the health of your local applicati
261.
by rdli 11y ago
Thanks for the pointer! This one, we hadn't seen. Based on a 5 minute read, my take would be 1) uses etcd (strongly consistent service discovery) 2) it looks like it is a centralized architecture, versus a distributed one and 3) it loo
262.
by rdli 11y ago
We made this because we discovered that lots of companies using microservices have independently converged on this type of architecture for load balancing (client-side HAProxy + integrated service discovery component + health checks), but
263.
Show HN: Baker Street – A simple client-side load balancer for microservices(bakerstreet.io)
83 points by rdli 11y ago|29 comments
264.
Baker St, a simple client-side load balancer for microservices(bakerstreet.io)
5 points by rdli 11y ago|1 comments